source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
This means BIT() can't be used in pre-processor conditional that
checks 'PAGE_SIZE > IXGBE_MAX_DATA_PER_TXD'.
Change to use a normal... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:22 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The current checks in GENMASK/BIT (eg reversed high/low) only work
for 'integer constant expressions' not 'compile-time constants'.
This is true for const_true() and -Wshift-count-overflow/negative.
While compile-time constants may be unusual, they can happen through
f... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:28 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Since all the GENMASK() values are compile-time constants they can
be tested with BUILD_BUG_ON() rather than KUNIT_EXPECT_EQ().
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
lib/tests/test_bits.c | 90 +++++++++++++++++++++----------------------
1 fi... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:30 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The definition of BIT() was moved from linux/bits.h to vdso/bits.h to
isolate the vdso from 'normal' kernel headers.
BIT_ULL() was then moved to be defined in the same place for consistency.
Since then linux/bits.h had gained BIT_Unn() and it really makes sense
for BI... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:29 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:29PM +0000, david.laight.linux@gmail.com wrote:
This is ugly.
Why can't the vDSO code make use of those checks, too?
Or use _BITUL() from the UAPI in the vDSO and remove vdso/bits.h. | {
"author": "Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de>",
"date": "Wed, 21 Jan 2026 16:17:18 +0100",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On 21/01/2026 at 15:57, david.laight.linux@gmail.com wrote:
Did those new checks actually found any real problem in the code? This
adds a lot of complexity so I am not sure whether this is a winning
trade-off.
But then, you only solve that shift problem for GENMASK() and
BIT(). Any other usage of the left/right shif... | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Wed, 21 Jan 2026 19:43:07 +0100",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, 21 Jan 2026 19:43:07 +0100
Vincent Mailhol <mailhol@kernel.org> wrote:
Not in an x86-64 allmodconfig build.
They might in a 32bit one where there have definitely been issues.
I suspect the compiler test will find more than sparse.
I liked getting that to work, but maybe it is OTT.
But the W=c is more gener... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Wed, 21 Jan 2026 19:14:48 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, 21 Jan 2026 16:17:18 +0100
Thomas Weißschuh <thomas.weissschuh@linutronix.de> wrote:
It works :-)
I could have put an #ifndef BIT in vdso/bits.h instead.
I didn't actually find anything that just needed vdso/bits.h
linux/bits.h would get included - eg (IIRC) because of warn_on_once().
I'm not that sure why... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Wed, 21 Jan 2026 19:24:51 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:18PM +0000, david.laight.linux@gmail.com wrote:
Sure!
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook | {
"author": "Kees Cook <kees@kernel.org>",
"date": "Wed, 21 Jan 2026 12:59:36 -0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 08:50:22 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 09:11:53 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 09:23:16 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 12:41:22 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 07:24:51PM +0000, David Laight wrote:
The #ifndef in vdso/bits.h is not much better IMO.
Given that there a multiple nicer options why not use on of those?
That is a bug. The vdso code should only include the vdso/ namespace.
Right now the inclusions are all over the place. I'd like to clean ... | {
"author": "Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de>",
"date": "Thu, 22 Jan 2026 08:39:42 +0100",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 09:11:53 +0800
kernel test robot <lkp@intel.com> wrote:
...
This might be a real bug.
The bit of mm.h is:
#define PP_DMA_INDEX_SHIFT (1 + __fls(PP_SIGNATURE - POISON_POINTER_DELTA))
#if POISON_POINTER_DELTA > 0
/* PP_SIGNATURE includes POISON_POINTER_DELTA, so limit the size of the DMA
* index ... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:25:54 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 09:23:16 +0800
kernel test robot <lkp@intel.com> wrote:
...
Unless I change BIT() back I'll change that to a static_assert().
David | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:30:29 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 12:41:22 +0800
kernel test robot <lkp@intel.com> wrote:
Can we stop sparse complaining about sizeof(VLA) ?
David | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:33:37 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 10:33:37AM +0000, David Laight wrote:
First of all, the LKP should install the fork of sparse by Al Viro. That will
fix tons of warnings that are related to modules and speed up the process
itself.
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Thu, 22 Jan 2026 16:26:44 +0200",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 16:26:44 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
The problem I have is I want to generate a compile time error inside:
__builtin_choose_expr(__is_constexpr(x), x && error_a(),
statically_true(y) && error_b());
Neither static_assert() nor a negative bitfield can be used ... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 14:55:56 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 10:25:54 +0000
David Laight <david.laight.linux@gmail.com> wrote:
I've managed to do an s390 cross build.
It is all quite obvious really.
For s390 PAGE_OFFSET is usually zero (I think kernel and user mappings are separate?).
This make PP_DMA_INDEX_BITS 0.
PP_SIGNATURE is 64 - so PP_DMA_INDEX_SHIFT... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 20:10:20 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 10:33:37AM +0000, David Laight wrote:
Got it, we will avoid the direct report this 'sparse: Variable length array is used' warning. | {
"author": "Philip Li <philip.li@intel.com>",
"date": "Fri, 23 Jan 2026 09:24:50 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 04:26:44PM +0200, Andy Shevchenko wrote:
Thanks Andy, i will switch to the repo from Al Viro for sparse. | {
"author": "Philip Li <philip.li@intel.com>",
"date": "Fri, 23 Jan 2026 09:25:36 +0800",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Adding the relevant parties to the discussion:
+To: Al Viro
+To: Chris Li
On 23/01/2026 at 02:25, Philip Li wrote:
Al Viro's fork just adds 8 commit on top of the upstream sparse repo.
Wouldn't it be possible to just merge those?
That would be much less confusing.
Yours sincerely,
Vincent Mailhol | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Fri, 23 Jan 2026 09:01:04 +0100",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 09:01:04AM +0100, Vincent Mailhol wrote:
Ideally yes, but you also should kick the distro's asses to update it, and
the sparse should bump its version...
Seems Al become a sparse maintainer de facto :-)
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 10:11:19 +0200",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 10:11:19AM +0200, Andy Shevchenko wrote:
Huh? What happened to Chris? FWIW, I do have some followups to that series
sitting locally; need to get that finished (mostly for proper __VA_OPT__
handling; that got stalled on the lovely corner cases where the interplay
with side effects of macro ex... | {
"author": "Al Viro <viro@zeniv.linux.org.uk>",
"date": "Fri, 23 Jan 2026 08:20:27 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 08:20:27AM +0000, Al Viro wrote:
I don't know, but upstream sparse haven't applied any solution for
MODULE*("FOO") stuff, nor reaction on my ping in that discussion
(I did it like week or so ago).
Thanks for doing all this!
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 10:24:01 +0200",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On 23/01/2026 at 09:24, Andy Shevchenko wrote:
After the project hiatus, I can imagine that there is some confusion :)
But Chris is back in his role of maintainer since September 2025. See:
- https://lore.kernel.org/linux-sparse/CACePvbXDO1ZybDu3RaFhED9D-9gC6LTMpWrxoh5xD+ZO5SLdzA@mail.gmail.com/
- https://git.ke... | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Fri, 23 Jan 2026 09:32:39 +0100",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 09:32:39AM +0100, Vincent Mailhol wrote:
...
My ping: https://lore.kernel.org/all/aV9vo7_turBr84bs@black.igk.intel.com/
But now I realised that there was another version of the series, and Chris
seems active there.
https://lore.kernel.org/all/CACePvbU5Pqo=bw_j8arOq16o1JBOSwPtuMZBVozy4FV7YsSLG... | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 10:46:37 +0200",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:22PM +0000, david.laight.linux@gmail.com wrote:
Thanks David,
Other than the motivation above, I appreciate that this removes two
#ifdefs, improving readability (subjective) and compile coverage
(objective) of this code.
As an aside: I'm Not sure what your merge plan is for this patchse... | {
"author": "Simon Horman <horms@kernel.org>",
"date": "Fri, 23 Jan 2026 15:44:25 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:18PM +0000, david.laight.linux@gmail.com wrote:
Thanks!
Reviewed-by: Yury Norov <ynorov@nvidia.com> | {
"author": "Yury Norov <ynorov@nvidia.com>",
"date": "Mon, 2 Feb 2026 11:45:28 -0500",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | HeeSu Kim <mlksvender@gmail.com> writes:
Are we sure this is in the correct commit hash? It is not present on
mainline.
Maybe it should be this one?
Fixes: abbf9a449441 ("rust: workaround `rustdoc` target modifiers bug")
Cheers,
C. Mitrodimas | {
"author": "Charalampos Mitrodimas <charmitro@posteo.net>",
"date": "Mon, 02 Feb 2026 13:59:54 +0000",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Tue, Feb 03, 2026, C. Mitrodimas wrote:
You're right. I mistakenly used a commit hash from my local branch.
I'll send a v2 with the correct Fixes tag. | {
"author": "HeeSu Kim <mlksvender@gmail.com>",
"date": "Tue, 3 Feb 2026 08:17:05 +0900",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Mon, Feb 2, 2026 at 2:21 PM HeeSu Kim <mlksvender@gmail.com> wrote:
Could you please elaborate on the issues you are seeing, e.g. how to
reproduce them?
The flag is only used to silence errors from checks that were added to
`rustc` and it is ignored otherwise (that is why the workaround was
written like that).
Th... | {
"author": "Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>",
"date": "Mon, 2 Feb 2026 15:20:01 +0100",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Mon Feb 2, 2026 at 10:21 PM GMT, HeeSu Kim wrote:
It looks like this bug has been fixed upstream already. While you're at it,
would you mind also add code so that we stop applying the workaround for
versions with bug fixed already?
Thanks,
Gary | {
"author": "\"Gary Guo\" <gary@garyguo.net>",
"date": "Mon, 02 Feb 2026 14:24:31 +0000",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Tue, Feb 03, 2026, Gary Guo wrote:
Sure, I'll check which Rust version includes the fix and send a patch
with the requested changes.
Best regards,
HeeSu Kim | {
"author": "HeeSu Kim <mlksvender@gmail.com>",
"date": "Tue, 3 Feb 2026 08:45:35 +0900",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | The `-Cunsafe-allow-abi-mismatch=fixed-x18` workaround was added to
handle a rustdoc bug (rust-lang/rust#144521) where target modifiers
were not properly saved.
This bug was fixed in Rust 1.90.0 (rust-lang/rust#144523). Restrict
the workaround to only apply for Rust 1.88.x and 1.89.x versions that
are affected by the ... | {
"author": "HeeSu Kim <mlksvender@gmail.com>",
"date": "Tue, 3 Feb 2026 09:21:16 +0900",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Mon, Feb 2, 2026 at 4:21 PM HeeSu Kim <mlksvender@gmail.com> wrote:
Normally these references should be full links (i.e. a tag), since we
do not have "autolinking" like GitHub e.g.
Link: https://........ [1]
Then you can use [1] above instead of the parenthesis.
To clarify a bit: avoiding the flags is good, b... | {
"author": "Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>",
"date": "Mon, 2 Feb 2026 17:00:59 +0100",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 | The `-Cunsafe-allow-abi-mismatch=fixed-x18` option is a workaround for
a rustdoc issue (rust-lang/rust#144521) where target modifiers were not
properly saved. This affects both rustdoc and doctests builds.
However, `fixed-x18` is an ARM64-specific ABI modifier related to the
x18 register reservation (used for Shadow C... | On Mon, 3 Feb 2026, Miguel Ojeda wrote:
Thanks for the detailed feedback.
For v3, I will:
- Use full Link: tags for GitHub references instead of shorthand
- Add Link: tag after Suggested-by pointing to Gary's lore message
- Remove the Fixes: tag
- Add Cc: stable@vger.kernel.org # Useful in 6.18.y and later.
Regardin... | {
"author": "HeeSu Kim <mlksvender@gmail.com>",
"date": "Tue, 3 Feb 2026 10:46:13 +0900",
"thread_id": "20260203014613.2708234-1-mlksvender@gmail.com.mbox.gz"
} |
lkml | [PATCH v2] PCI: s32g: Fix ports parsing | No error return is missing after the loop resulting in removing the
ports from the list.
Fixes: 5cbc7d3e316e ("PCI: s32g: Add NXP S32G PCIe controller driver (RC)")
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
---
Change since v1:
- handle correctly the case when there is no child port
drivers/pci/co... | On Mon, Feb 02, 2026 at 04:10:50PM +0100, Vincent Guittot wrote:
break and goto is logical equal here. So only need below if (ret).
Frank | {
"author": "Frank Li <Frank.li@nxp.com>",
"date": "Mon, 2 Feb 2026 12:42:46 -0500",
"thread_id": "aYDiFpGT5hEDDFhV@lizhi-Precision-Tower-5810.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
This file actually implements irq remapping, so rename to more appropriate
hyperv-irq.c. A new file named hyperv-iommu.c will be introduced later.
Also, move CONFIG_IRQ_REMAP out of the file and add to Makefile.
Signed-off-by: Mukesh Rathor <mrathor@linux.microsoft.co... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:16 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Many PCI passthru related hypercalls require partition id of the target
guest. Guests are actually managed by MSHV driver and the partition id
is only maintained there. Add a field in the partition struct in MSHV
driver to save the tgid of the VMM process creating the ... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:19 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Passthru exposes insufficient memory hypercall failure in the current map
device interrupt hypercall. In case of such a failure, we must deposit
more memory and redo the hypercall. Add support for that. Deposit memory
needs partition id, make that a parameter to the ma... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:18 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Main change here is to rename hv_compose_msi_msg to
hv_vmbus_compose_msi_msg as we introduce hv_compose_msi_msg in upcoming
patches that builds MSI messages for both VMBus and non-VMBus cases. VMBus
is not used on baremetal root partition for example. While at it, repl... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:23 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Add ioctl support for creating MSHV devices for a paritition. At
present only VFIO device types are supported, but more could be
added. At a high level, a partition ioctl to create device verifies
it is of type VFIO and does some setup for bridge code in mshv_vfio.c.
A... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:22 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Add data structs needed by the subsequent patch that introduces a new
module to implement VFIO-MSHV pseudo device.
Signed-off-by: Mukesh Rathor <mrathor@linux.microsoft.com>
---
drivers/hv/mshv_root.h | 23 +++++++++++++++++++++++
include/uapi/linux/mshv.h | 31 ++... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:20 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Make cosmetic changes:
o Rename struct pci_dev *dev to *pdev since there are cases of
struct device *dev in the file and all over the kernel
o Rename hv_build_pci_dev_id to hv_build_devid_type_pci in anticipation
of building different types of device ids
o Fix... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:17 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Add a new file to implement VFIO-MSHV bridge pseudo device. These
functions are called in the VFIO framework, and credits to kvm/vfio.c
as this file was adapted from it.
Original author: Wei Liu <wei.liu@kernel.org>
(Slightly modified from the original version).
Sign... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:21 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
As mentioned previously, a direct attached device must be referenced
via logical device id which is formed in the initial attach hypercall.
Interrupt mapping paths for direct attached devices are almost same,
except we must use logical device ids instead of the PCI dev... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:28 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Upon guest access, in case of missing mmio mapping, the hypervisor
generates an unmapped gpa intercept. In this path, lookup the PCI
resource pfn for the guest gpa, and ask the hypervisor to map it
via hypercall. The PCI resource pfn is maintained by the VFIO driver,
a... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:30 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
VFIO no longer puts the mmio pfn in vma->vm_pgoff. So, remove code
that is using it to map mmio space. It is broken and will cause
panic.
Signed-off-by: Mukesh Rathor <mrathor@linux.microsoft.com>
---
drivers/hv/mshv_root_main.c | 20 ++++----------------
1 file chan... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:29 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Import/copy from Hyper-V public headers, definitions and declarations that
are related to attaching and detaching of device domains and interrupt
remapping, and building device ids for those purposes.
Signed-off-by: Mukesh Rathor <mrathor@linux.microsoft.com>
---
inc... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:24 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
On Hyper-V, most hypercalls related to PCI passthru to map/unmap regions,
interrupts, etc need a device id as a parameter. This device id refers
to that specific device during the lifetime of passthru.
An L1VH VM only contains VMBus based devices. A device id for a VM... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:25 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
On Hyper-V, most hypercalls related to PCI passthru to map/unmap regions,
interrupts, etc need a device id as a parameter. A device id refers
to a specific device. A device id is of two types:
o Logical: used for direct attach (see below) hypercalls. A logical
... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:26 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Add a new file to implement management of device domains, mapping and
unmapping of iommu memory, and other iommu_ops to fit within the VFIO
framework for PCI passthru on Hyper-V running Linux as root or L1VH
parent. This also implements direct attach mechanism for PCI ... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 19 Jan 2026 22:42:27 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:21PM -0800, Mukesh R wrote:
There is a Linux standard for giving credits when code is adapted from.
This doesn't follow that standard. Please fix.
This put must be sync as device must be detached from domain before
attempting partition destruction.
This was explicitly mentioned in the p... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 08:09:02 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:22PM -0800, Mukesh R wrote:
Shouldn't the partition be put here?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 08:13:55 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on pci/next pci/for-linus arm64/for-next/core clk/clk-next soc/for-next linus/master arnd-asm-generic/master v6.19-rc6 next-20260119]
[If your patch is applied to the wrong git tree, kindly ... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Wed, 21 Jan 2026 03:08:24 +0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on pci/next pci/for-linus arm64/for-next/core soc/for-next linus/master v6.19-rc6]
[cannot apply to clk/clk-next arnd-asm-generic/master next-20260119]
[If your patch is applied to the... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Wed, 21 Jan 2026 03:52:58 +0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on pci/next pci/for-linus arm64/for-next/core clk/clk-next soc/for-next linus/master arnd-asm-generic/master v6.19-rc6 next-20260120]
[If your patch is applied to the wrong git tree, k... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Wed, 21 Jan 2026 05:09:48 +0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
On Mon, 19 Jan 2026 22:42:15 -0800
Mukesh R <mrathor@linux.microsoft.com> wrote:
I think some introduction/background to L1VH would help.
It may be clearer to state that the hypervisor supports Linux IOMMU
paging domains through map/unmap hypercalls, mapping GPAs to HPAs using
stage‑2 I/O page tables.
Th... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 13:50:32 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:24PM -0800, Mukesh R wrote:
<snip>
Shouldn't the inner struct be packed instead?
Why should the union be packed?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 14:17:24 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:25PM -0800, Mukesh R wrote:
Why not moving this static function definition above the called instead of
defining the prototype?
This variable is redundant.
It looks like this value always fits into 32 bit, so what is the value
in returning 64 bit?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 14:22:23 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:26PM -0800, Mukesh R wrote:
Should this one be renamed into hv_build_devid_type_vmbus() to align
with the other two function names?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 14:27:33 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:27PM -0800, Mukesh R wrote:
<snip>
The return above is never reached.
hvdom varaible is redundant.
Why goto here and not return NULL like above?
Shouldn't this be modified iff the detach succeeded?
There is some inconsistency in namings and behaviour of paired
functions:
1. The ... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 16:12:42 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:28PM -0800, Mukesh R wrote:
l1vh and root are mutually exclusive partitions.
If you wanted to highlight that it's l1vh itself and not its child guest, then
"l1vh parent" term would do.
Looks like the only special case is for attached logical devices,
otherwise hv_current_partition_id is... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 16:47:07 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on pci/next pci/for-linus arm64/for-next/core clk/clk-next soc/for-next linus/master v6.19-rc6 next-20260120]
[cannot apply to arnd-asm-generic/master]
[If your patch is applied to the... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Wed, 21 Jan 2026 08:53:50 +0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:29PM -0800, Mukesh R wrote:
No need updating ret here: it's 0 after the previous call.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 17:41:39 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:30PM -0800, Mukesh R wrote:
Semaphore can't be taken under spinlock.
Get it instead.
Why this check is needed again?
The region type is stored on the region itself.
And the type is checked on the caller side.
This call needs to be protected by the spinlock.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 20 Jan 2026 17:53:29 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
On Mon, 19 Jan 2026 22:42:27 -0800
Mukesh R <mrathor@linux.microsoft.com> wrote:
Given we are also developing a guest iommu driver on hyperv, I think it
is more clear to name them accordingly. Perhaps, hyperv-iommu-root.c?
Will this driver be x86 only?
DMA and IRQ remapping should be separate
I don't th... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Wed, 21 Jan 2026 21:18:06 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/19/2026 10:42 PM, Mukesh R wrote:
This should go inside the #if IS_ENABLED(CONFIG_MSHV_ROOT) section. | {
"author": "Nuno Das Neves <nunodasneves@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 10:23:04 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/19/2026 10:42 PM, Mukesh R wrote:
With this commit, the IOCTL number is exposed to userspace but it doesn't work.
Ideally the IOCTL number should be added in the commit where it becomes usable. | {
"author": "Nuno Das Neves <nunodasneves@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 10:25:36 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/19/2026 10:42 PM, Mukesh R wrote:
Since the code is very similar to Wei's original commit, the way I'd
recommend to do it is:
1. Change the commit author to Wei, using git commit --amend --author=
and
2. Put his signed-off line before yours:
Signed-off-by: Wei Liu <wei.liu@kernel.org>
Signed-off-by: Mukesh Ratho... | {
"author": "Nuno Das Neves <nunodasneves@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 10:32:09 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/19/2026 10:42 PM, Mukesh R wrote:
What is the reason for having this as a separate commit from patch 15?
It seems like removing this code and adding the mmio intercept
handling could be done in one patch. | {
"author": "Nuno Das Neves <nunodasneves@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 10:34:55 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/23/26 10:25, Nuno Das Neves wrote:
Correct, I switched it because the next patch won't compile without it as
it needs the declarations here. It could be combined into one big patch,
but I think normally one would not expect full functionality until the
release is certified to be that feature compliant anyways. H... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:36:28 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/23/26 10:32, Nuno Das Neves wrote:
Perfect! Thank you, that is exactly the information I was trying to
seek... makes sense.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:37:34 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 14:17, Stanislav Kinsburskii wrote:
From GCC docs:
Specifying this attribute for struct and union types is equivalent to
specifying the packed attribute on each of the structure or union members.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:38:56 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 14:22, Stanislav Kinsburskii wrote:
Did you see the function implementation? It has other dependencies that
are later, it would need code reorg.
Thanks,
-Mukesh
Not really. It helps with debug by putting a quick print, and is
harmless.
The ABI has device id defined as 64bits where this is assigned.
T... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:42:54 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 14:27, Stanislav Kinsburskii wrote:
No, because hyperv only defines two types of device ids, and it would
unnecessary at to confusion. vmbus uses one the two types of device
ids. | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:44:01 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 16:12, Stanislav Kinsburskii wrote:
Some debug code there got removed. Will fix in next version.
We want to still free the domain and not let it get stuck. The purpose
is more to make sure detach was called before domain free.
The pair of hv_iommu_unmap_pages is hv_iommu_map_pages right above.
hv_iommu_... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 17:26:19 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/21/26 21:18, Jacob Pan wrote:
well, l1vh is not quite root, more like a parent. But we've been using
l1vh root loosely to mean l1vh parent. so probably ok to rename it
to hyperv-iommu-root.c. I prefer not calling it parent or something
like that.
j
Yes for now.
not sure i follow.
Well, it is getting the inf... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 18:01:29 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 16:47, Stanislav Kinsburskii wrote:
We've been loosely using "l1vh root" to mean "privilated l1vh" as opposed
to l1vh guests. I think that is fine. l1vh parent is confusing, as it may
also refer to l1vh parent, which would be the host. so as long as the
context is clear, we are ok.
Could be, but at the co... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 18:08:49 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/23/26 10:34, Nuno Das Neves wrote:
Just ease of review and porting patches from this branch to that
branch to that release to this release... I am sure someone would
have asked for this to be a separate patch :).
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 18:12:14 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 17:53, Stanislav Kinsburskii wrote:
Yeah, something didn't feel right here and I meant to recheck, now regret
rushing to submit the patch.
Rethinking, I think the pt_mem_regions_lock is not needed to protect
the uaddr because unmap will properly serialize via the mm lock.
To make sure region did not cha... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 18:19:15 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/20/26 13:50, Jacob Pan wrote:
Ok, i can add something, but l1vh was very well introduced if you
search the mshv commits for "l1vh".
sure.
Yeah, I was hoping we can get by for now without it. At least in case of
the cloud hypervisor, entire guest ram is mapped anyways. We can document
it and work on enhancemen... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 18:27:34 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 23, 2026 at 05:26:19PM -0800, Mukesh R wrote:
<snip>
How can one debug subseqent errors if num_attchd is decremented
unconditionally? In reality the device is left attached, but the related
kernel metadata is gone.
Hv_iommu_map_pages is a wrapper around hv_iommu_map_pgs while
hv_iommu_unmap_pages is a ... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 07:57:35 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 23, 2026 at 06:19:15PM -0800, Mukesh R wrote:
How can this happen? One can't change VMA type without unmapping it
first. And unmapping it leads to a kernel MMIO region state dangling
around without corresponding user space mapping.
This is similar to dangling pinned regions and should likely be
addressed... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 10:15:53 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 23, 2026 at 04:42:54PM -0800, Mukesh R wrote:
Why not placing the caller side after the function definition then?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 12:50:03 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/26/26 07:57, Stanislav Kinsburskii wrote:
Error is printed in case of failed detach. If there is panic, at least
you can get some info about the device. Metadata in hypervisor is
around if failed.
Unmap does not need intermediate function.
We print error upon its failure in hv_iommu_map_pages():
... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 19:02:29 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/26/26 10:15, Stanislav Kinsburskii wrote:
Right, and vm_flags would not be mmio expected then.
I don't think we need that. Either it succeeds if the region did not
change at all, or just fails.
I am not sure why? This check is done by a vcpu thread, so regions
will not have just gone away.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 19:07:22 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 26, 2026 at 07:02:29PM -0800, Mukesh R wrote:
With this approach the only thing left is a kernel message.
But if the state is kept intact, one could collect a kernel core and
analyze it.
And note, that there won't be a hypervisor core by default: our main
context with the usptreamed version of the driver ... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 10:46:49 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 26, 2026 at 07:07:22PM -0800, Mukesh R wrote:
I'm afraid we do, as if the driver mapped a page with the previous
memory region, and then the region is unmapped, the page will stay
mapped in the hypervisor, but will be considered free by kernel, which
in turn will lead to GPF upn next allocation.
With pinn... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 10:57:08 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
On Fri, 23 Jan 2026 18:01:29 -0800
Mukesh R <mrathor@linux.microsoft.com> wrote:
yeah, something specific and different than the guest driver will do.
If there is nothing x86 specific in this driver (assuming the
hypercalls here are not x86 only), maybe you can move to the generic
startup code.
In IOMMU ... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 11:21:44 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | Hi Mukesh,
On second thought, if the hv_no_attdev knob is only meant to control
host domain attach vs. direct attach, then it is irrelevant on L1VH.
Would it make more sense to rename this to something like
hv_host_disable_direct_attach? That would better reflect its scope and
allow it to be ignored under L1VH, and r... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 14:31:19 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Mon, Jan 19, 2026 at 10:42:23PM -0800, Mukesh R wrote:
Don't mix up cleanup changes. Do it in a separate patch.
- Mani
--
மணிவண்ணன் சதாசிவம் | {
"author": "Manivannan Sadhasivam <mani@kernel.org>",
"date": "Wed, 28 Jan 2026 19:33:57 +0530",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 23, 2026 at 04:42:54PM -0800, Mukesh R wrote:
Such debug print do not exist now. So there is no need of a variable, drop it.
- Mani
--
மணிவண்ணன் சதாசிவம் | {
"author": "Manivannan Sadhasivam <mani@kernel.org>",
"date": "Wed, 28 Jan 2026 20:06:21 +0530",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/27/26 14:31, Jacob Pan wrote:
It would, but it is kernel parameter and needs to be terse. It would
be documented properly tho, so we should be ok.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 14:10:57 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/27/26 10:57, Stanislav Kinsburskii wrote:
There are no ram pages for mmio regions. Also, we don't do much with
mmio regions other than tell the hyp about it.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 14:17:24 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/27/26 10:46, Stanislav Kinsburskii wrote:
Again, most of linux stuff is cleaned up, the only state is in
hypervisor, and hypervisor can totally protect itself and devices.
So there is not much in kernel core as it got cleaned up already.
Think of this as additional check, we can remove in future after
it stands t... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 14:51:19 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/27/26 11:21, Jacob Pan wrote:
It's x86 specific:
x86_init.iommu.iommu_init = hv_iommu_init
oh, you are talking about the config option, yeah, I will move
CONFIG_IRQ_REMAP from Kconfig to here.
it could, but by convention all public funcs here are hv_iommu_xxx..
and other reviewers might object... W... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 15:44:37 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 30, 2026 at 02:51:19PM -0800, Mukesh R wrote:
Again, the hypervisor state is not accessible from the kernel core in
L1VH.
In upstream, it does not matter what the work is focused on. The only
thing that matters is that the functionality is merged and available.
Once the code is merged upstream, it become... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 08:20:37 -0800",
"thread_id": "aYDO1S3DdUSHNkEY@skinsburskii.localdomain.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.