On Fri, Sep 27, 2024 at 01:54:45PM +0800, Yi Liu wrote:
> > > > Baolu told me that Intel may have the same: different domain IDs
> > > > on different IOMMUs; multiple IOMMU instances on one chip:
> > > > https://lore.kernel.org/linux-iommu/cf4fe15c-8bcb-4132-a1fd-b2c8ddf27...@linux.intel.com/
> > >
On Fri, Sep 27, 2024 at 01:38:08PM +0800, Yi Liu wrote:
> > > Does it mean each vIOMMU of VM can only have
> > > one s2 HWPT?
> >
> > Giving some examples here:
> > - If a VM has 1 vIOMMU, there will be 1 vIOMMU object in the
> > kernel holding one S2 HWPT.
> > - If a VM has 2 vIOMMUs, the
From: zhang jiao
Path is not initialized before use,
remove the unnecessary remove function.
Signed-off-by: zhang jiao
---
tools/testing/selftests/powerpc/mm/tlbie_test.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/powerpc/mm/tlbie_test.c
b/tools/testing/selftes
On 2024/9/27 10:05, Baolu Lu wrote:
On 9/27/24 4:03 AM, Nicolin Chen wrote:
On Thu, Sep 26, 2024 at 04:47:02PM +0800, Yi Liu wrote:
On 2024/9/26 02:55, Nicolin Chen wrote:
On Wed, Sep 25, 2024 at 06:30:20PM +0800, Yi Liu wrote:
Hi Nic,
On 2024/8/28 00:59, Nicolin Chen wrote:
This series int
From: zhang jiao
There is no va_end after va_copy, just add it.
Signed-off-by: zhang jiao
---
tools/testing/selftests/net/tcp_ao/lib/aolib.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/net/tcp_ao/lib/aolib.h
b/tools/testing/selftests/net/tcp_ao/lib/aolib.h
inde
On 2024/9/27 04:03, Nicolin Chen wrote:
On Thu, Sep 26, 2024 at 04:47:02PM +0800, Yi Liu wrote:
On 2024/9/26 02:55, Nicolin Chen wrote:
On Wed, Sep 25, 2024 at 06:30:20PM +0800, Yi Liu wrote:
Hi Nic,
On 2024/8/28 00:59, Nicolin Chen wrote:
This series introduces a new VIOMMU infrastructure a
On Fri, Sep 27, 2024 at 12:49:07AM +0200, Frederic Weisbecker wrote:
> kthread_create() creates a kthread without running it yet. kthread_run()
> creates a kthread and runs it.
>
> On the other hand, kthread_create_worker() creates a kthread worker and
> runs it.
>
> This difference in behaviours
On 2024/9/27 04:10, Nicolin Chen wrote:
On Thu, Sep 26, 2024 at 04:50:46PM +0800, Yi Liu wrote:
On 2024/8/28 00:59, Nicolin Chen wrote:
Now a VIOMMU can wrap a shareable nested parent HWPT. So, it can act like
a nested parent HWPT to allocate a nested HWPT.
Support that in the IOMMU_HWPT_ALLOC
The hmm2 double_map test was failing due to an incorrect
buffer->mirror size. The buffer->mirror size was 6, while buffer->ptr
size was 6 * PAGE_SIZE. The test failed because the kernel's
copy_to_user function was attempting to copy a 6 * PAGE_SIZE buffer
to buffer->mirror. Since the size of buffer
On Thu, Sep 26, 2024 at 09:14:11PM -0700, Guenter Roeck wrote:
> Hi Stephen,
>
> On Thu, Jul 18, 2024 at 02:05:07PM -0700, Stephen Boyd wrote:
> > Test that clks registered with 'struct clk_parent_data' work as
> > intended and can find their parents.
> >
>
> When testing this on arm64, I see th
On Fri, Sep 27, 2024 at 03:20:40AM +0200, Mathieu Desnoyers wrote:
> On 2024-09-26 18:12, Linus Torvalds wrote:
> > On Thu, 26 Sept 2024 at 08:54, Jonas Oberhauser
> > wrote:
> > >
> > > No, the issue introduced by the compiler optimization (or by your
> > > original patch) is that the CPU can sp
On Fri, Sep 27, 2024 at 09:37:50AM +0800, Boqun Feng wrote:
>
>
> On Fri, Sep 27, 2024, at 9:30 AM, Mathieu Desnoyers wrote:
> > On 2024-09-27 02:01, Boqun Feng wrote:
> >>#define ADDRESS_EQ(var, expr)
> >> \
> >>({
Hi Stephen,
On Thu, Jul 18, 2024 at 02:05:07PM -0700, Stephen Boyd wrote:
> Test that clks registered with 'struct clk_parent_data' work as
> intended and can find their parents.
>
When testing this on arm64, I see the error below. The error is only
seen if I boot through efi, i.e., with "-bios
The include.sh file is generated for inclusion and should not be executable.
Otherwise, it will be added to kselftest-list.txt. Additionally, add the
executable bit for test.py at the same time to ensure proper functionality.
Fixes: 3ade6ce1255e ("selftests: rds: add testing infrastructure")
Signe
From: zhang jiao
There is a memory leak in mkdirty, just free src before return.
Signed-off-by: zhang jiao
---
tools/testing/selftests/mm/mkdirty.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/mm/mkdirty.c
b/tools/testing/selftests/mm/mkdirty.c
index 1db134063c3
On Fri, Sep 27, 2024 at 02:23:16AM +, Tian, Kevin wrote:
> > > > > Does it mean each vIOMMU of VM can only have
> > > > > one s2 HWPT?
> > > >
> > > > Giving some examples here:
> > > > - If a VM has 1 vIOMMU, there will be 1 vIOMMU object in the
> > > >kernel holding one S2 HWPT.
> > > >
Hi,
Could someone help to review it or provide suggestions?
Any comments are welcome.
This patch is intended to allow the rproc driver to handle the
following use-after-free issue:
### UAF log
[ 337.540275][ T470] virtqueue_add.llvm.10153462284424984632+0xb48/0
xcc4
[ 337.546969][ T470] v
On Fri, Sep 27, 2024 at 12:43:16AM +, Tian, Kevin wrote:
> > From: Nicolin Chen
> > Sent: Friday, September 27, 2024 4:11 AM
> >
> > On Thu, Sep 26, 2024 at 04:50:46PM +0800, Yi Liu wrote:
> > > On 2024/8/28 00:59, Nicolin Chen wrote:
> > > > Now a VIOMMU can wrap a shareable nested parent HWP
> From: Nicolin Chen
> Sent: Friday, September 27, 2024 9:26 AM
>
> On Fri, Sep 27, 2024 at 12:43:16AM +, Tian, Kevin wrote:
> > > From: Nicolin Chen
> > > Sent: Friday, September 27, 2024 4:11 AM
> > >
> > > On Thu, Sep 26, 2024 at 04:50:46PM +0800, Yi Liu wrote:
> > > > On 2024/8/28 00:59,
On 9/27/24 4:03 AM, Nicolin Chen wrote:
On Thu, Sep 26, 2024 at 04:47:02PM +0800, Yi Liu wrote:
On 2024/9/26 02:55, Nicolin Chen wrote:
On Wed, Sep 25, 2024 at 06:30:20PM +0800, Yi Liu wrote:
Hi Nic,
On 2024/8/28 00:59, Nicolin Chen wrote:
This series introduces a new VIOMMU infrastructure a
On 2024-09-27 02:01, Boqun Feng wrote:
#define ADDRESS_EQ(var, expr)
\
({
\
bool _cmp_res = (unsigned long)(var) == (unsigned
long)
On Fri, Sep 27, 2024, at 9:30 AM, Mathieu Desnoyers wrote:
> On 2024-09-27 02:01, Boqun Feng wrote:
>> #define ADDRESS_EQ(var, expr)
>> \
>> ({
>> \
>>
On 2024-09-26 18:12, Linus Torvalds wrote:
On Thu, 26 Sept 2024 at 08:54, Jonas Oberhauser
wrote:
No, the issue introduced by the compiler optimization (or by your
original patch) is that the CPU can speculatively load from the first
pointer as soon as it has completed the load of that pointer
> From: Nicolin Chen
> Sent: Friday, September 27, 2024 4:11 AM
>
> On Thu, Sep 26, 2024 at 04:50:46PM +0800, Yi Liu wrote:
> > On 2024/8/28 00:59, Nicolin Chen wrote:
> > > Now a VIOMMU can wrap a shareable nested parent HWPT. So, it can act
> like
> > > a nested parent HWPT to allocate a nested
On Thu, Sep 26, 2024 at 09:54:33AM -0700, Linus Torvalds wrote:
> On Thu, 26 Sept 2024 at 09:40, Jonas Oberhauser
> wrote:
> >
> > Boqun seems to be unhappy with a barrier though, because it would
> > theoretically also forbid unrelated optimizations.
>
> Well, doing a "barrier()" is kind of a bi
On 9/24/24 12:25, Michal Luczaj wrote:
> On 8/19/24 22:05, Jakub Sitnicki wrote:
>> On Wed, Aug 14, 2024 at 06:14 PM +02, Michal Luczaj wrote:
>>> On 8/6/24 19:45, Jakub Sitnicki wrote:
On Tue, Aug 06, 2024 at 07:18 PM +02, Michal Luczaj wrote:
> Great, thanks for the review. With this com
Hi Matt,
On Wed, Sep 25, 2024 at 11:39 PM Matthew Maurer wrote:
>
> This patch series is intended for use alongside the Implement
> MODVERSIONS for RUST [1] series as a replacement for the symbol name
> hashing approach used there to enable RUST and MODVERSIONS at the same
> time.
>
> Elsewhere,
Now that kthreads have an infrastructure to handle preferred affinity
against CPU hotplug and housekeeping cpumask, convert RCU exp workers to
use it instead of handling all the constraints by itself.
Acked-by: Paul E. McKenney
Signed-off-by: Frederic Weisbecker
---
kernel/rcu/tree.c | 105
kthread_create() creates a kthread without running it yet. kthread_run()
creates a kthread and runs it.
On the other hand, kthread_create_worker() creates a kthread worker and
runs it.
This difference in behaviours is confusing. Also there is no way to
create a kthread worker and affine it using
kthread_create_on_cpu() uses the CPU argument as an implicit and unique
printf argument to add to the format whereas
kthread_create_worker_on_cpu() still relies on explicitly passing the
printf arguments. This difference in behaviour is error prone and
doesn't help standardizing per-CPU kthread nam
Now that kthreads have an infrastructure to handle preferred affinity
against CPU hotplug and housekeeping cpumask, convert RCU boost to use
it instead of handling all the constraints by itself.
Acked-by: Paul E. McKenney
Signed-off-by: Frederic Weisbecker
---
kernel/rcu/tree.c| 27
Affining kthreads follow either of four existing different patterns:
1) Per-CPU kthreads must stay affine to a single CPU and never execute
relevant code on any other CPU. This is currently handled by smpboot
code which takes care of CPU-hotplug operations.
2) Kthreads that _have_ to be aff
Kthreads attached to a preferred NUMA node for their task structure
allocation can also be assumed to run preferrably within that same node.
A more precise affinity is usually notified by calling
kthread_create_on_cpu() or kthread_bind[_mask]() before the first wakeup.
For the others, a default a
Make sure the kthread is sleeping in the schedule_preempt_disabled()
call before calling its handler when kthread_bind[_mask]() is called
on it. This provides a sanity check verifying that the task is not
randomly blocked later at some point within its function handler, in
which case it could be ju
When a kthread or any other task has an affinity mask that is fully
offline or unallowed, the scheduler reaffines the task to all possible
CPUs as a last resort.
This default decision doesn't mix up very well with nohz_full CPUs that
are part of the possible cpumask but don't want to be disturbed
On Thu, Sep 26, 2024 at 04:50:46PM +0800, Yi Liu wrote:
> On 2024/8/28 00:59, Nicolin Chen wrote:
> > Now a VIOMMU can wrap a shareable nested parent HWPT. So, it can act like
> > a nested parent HWPT to allocate a nested HWPT.
> >
> > Support that in the IOMMU_HWPT_ALLOC ioctl handler, and update
On Thu, Sep 26, 2024 at 04:47:02PM +0800, Yi Liu wrote:
> On 2024/9/26 02:55, Nicolin Chen wrote:
> > On Wed, Sep 25, 2024 at 06:30:20PM +0800, Yi Liu wrote:
> > > Hi Nic,
> > >
> > > On 2024/8/28 00:59, Nicolin Chen wrote:
> > > > This series introduces a new VIOMMU infrastructure and related ioc
Hello, Michal.
On Thu, Sep 26, 2024 at 08:10:35PM +0200, Michal Koutný wrote:
...
> On Tue, Sep 10, 2024 at 11:01:07AM GMT, Tejun Heo wrote:
> > I think it's as useful as system-wide nice metric is.
>
> Exactly -- and I don't understand how that system-wide value (without
> any cgroups) is usefu
On Thu, 26 Sept 2024 at 08:54, Jonas Oberhauser
wrote:
>
> No, the issue introduced by the compiler optimization (or by your
> original patch) is that the CPU can speculatively load from the first
> pointer as soon as it has completed the load of that pointer:
You mean the compiler can do it. The
On Thu, Sep 26, 2024 at 5:22 AM Christophe Leroy
wrote:
>
>
>
> Le 26/09/2024 à 01:38, Matthew Maurer a écrit :
> > Adds a new format for MODVERSIONS which stores each field in a separate
> > ELF section. This initially adds support for variable length names, but
> > could later be used to add add
On Mon, Sep 23, 2024 at 07:20:04AM GMT, Joshua Hahn
wrote:
> From: Joshua Hahn
>
> v2 -> v3: Signed-off-by & renamed subject for clarity.
> v1 -> v2: Edited commit messages for clarity.
Thanks for the version changelog, appreciated!
...
> Exposing this metric will allow users to accurately pr
On Mon, Sep 23, 2024 at 07:20:05AM GMT, Joshua Hahn
wrote:
> static void cgroup_base_stat_flush(struct cgroup *cgrp, int cpu)
> @@ -535,7 +537,10 @@ void __cgroup_account_cputime_field(struct cgroup *cgrp,
>
> switch (index) {
> case CPUTIME_USER:
> + rstatc->bstat.cput
On Mon, Sep 23, 2024 at 07:20:06AM GMT, Joshua Hahn
wrote:
> +/*
> + * Creates a nice process that consumes CPU and checks that the elapsed
> + * usertime in the cgroup is close to the expected time.
> + */
> +static int test_cpucg_nice(const char *root)
> +{
> + int ret = KSFT_FAIL;
> +
Fix a typo in an email address.
Reported-by: Konstantin Ryabitsev
Closes:
https://lore.kernel.org/all/20240925-rational-succinct-vulture-cca9fb@lemur/T/
Signed-off-by: Alexey Makhalov
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTA
From: Geliang Tang
This patch adds a "cgroup/getsockopt" way to inspect the subflows of an
MPTCP socket, and verify the modifications done by the same BPF program
in the previous commit: a different mark per subflow, and a different
TCP CC set on the second one. This new hook will be used by the
From: Geliang Tang
This patch adds a subtest named test_subflow in test_mptcp to load and
verify the newly added MPTCP subflow BPF program. To goal is to make
sure it is possible to set different socket options per subflows, while
the userspace socket interface only lets the application to set th
From: Nicolas Rybowski
Move Nicolas' patch into bpf selftests directory. This example adds a
different mark (SO_MARK) on each subflow, and changes the TCP CC only on
the first subflow.
>From the userspace, an application can do a setsockopt() on an MPTCP
socket, and typically the same value will
In this series from Geliang, modifying MPTCP BPF selftests, we have:
- A new MPTCP subflow BPF program setting socket options per subflow: it
looks better to have this old test program in the BPF selftests to
track regressions and to serve as example.
Note: Nicolas is no longer working at T
The pull request you sent on Wed, 25 Sep 2024 07:09:49 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0181f8c809d6116a8347d8beb25a8c35ed22f7d7
Thank you!
--
Deet-doot-dot, I am a b
On 9/26/24 18:40, Uladzislau Rezki wrote:
> On Thu, Sep 26, 2024 at 06:35:27PM +0200, Vlastimil Babka wrote:
>> On 9/18/24 16:40, Uladzislau Rezki wrote:
>> >>
>> > Thank you for valuable feedback! Indeed it is hard to follow, even
>> > though it works correctly.
>> > I will add the comment and als
On Tue, Sep 24 2024 at 09:56, Shuah Khan wrote:
> The first patch in this two patch fixes warn_unused_result compile
> time warning in posix_timers test.
>
> The second patch removes local NSEC_PER_SEC and USEC_PER_SEC defines.
> NSEC_PER_SEC and USEC_PER_SEC are defines in several timers tests.
>
On Thu, Sep 26, 2024 at 06:46:29PM +0200, Vlastimil Babka wrote:
> On 9/26/24 18:40, Uladzislau Rezki wrote:
> > On Thu, Sep 26, 2024 at 06:35:27PM +0200, Vlastimil Babka wrote:
> >> On 9/18/24 16:40, Uladzislau Rezki wrote:
> >> >>
> >> > Thank you for valuable feedback! Indeed it is hard to follo
On Thu, 26 Sept 2024 at 09:40, Jonas Oberhauser
wrote:
>
> Boqun seems to be unhappy with a barrier though, because it would
> theoretically also forbid unrelated optimizations.
Well, doing a "barrier()" is kind of a big hammer thing, but honestly,
I don't think we've ever seen any real situation
On 9/18/24 16:40, Uladzislau Rezki wrote:
>>
> Thank you for valuable feedback! Indeed it is hard to follow, even
> though it works correctly.
> I will add the comment and also break the loop on first queuing as you
> suggested!
>
> It does not make sense to loop further because following iteratio
On 26.09.24 17:20, David Hildenbrand wrote:
Of course, just after I sent it:
Subject: s/hguetlb/hugetlb/
--
Cheers,
David / dhildenb
Am 9/26/2024 um 6:12 PM schrieb Linus Torvalds:
On Thu, 26 Sept 2024 at 08:54, Jonas Oberhauser
wrote:
No, the issue introduced by the compiler optimization (or by your
original patch) is that the CPU can speculatively load from the first
pointer as soon as it has completed the load of that
On Thu, Sep 26, 2024 at 06:35:27PM +0200, Vlastimil Babka wrote:
> On 9/18/24 16:40, Uladzislau Rezki wrote:
> >>
> > Thank you for valuable feedback! Indeed it is hard to follow, even
> > though it works correctly.
> > I will add the comment and also break the loop on first queuing as you
> > sugg
Add an explicit MODULE_VERSION("0.0.1") specification
for a vhost_vsock module. It is useful because it allows
userspace to check if vhost_vsock is there when it is
configured as a built-in.
Without this change, there is no /sys/module/vhost_vsock directory.
With this change:
$ ls -la /sys/module
...
> The checksums for the randomly-generated test cases were calculated
> using a reference implementation [1] and this test compares them against
> the values yielded by the kernel's implementation.
I'd just use a naïve implementation - doesn't really matter
if it is a bit slow.
Slow is relati
Hi Mark,
Hope you are doing great.
I am interested to work on ARM64 livepatching using SFrame, and thus,
reinitiating the old thread (Link:
https://lore.kernel.org/all/ZXxO43Xwn5GHsrO8@FVFF77S0Q05N/).
Please do let me know if there anything which I can help with, in developing
this feature. T
On 9/26/24 09:20, David Hildenbrand wrote:
We currently assume that the hugetlb page size is 2 MiB, which is
why we mmap() a 2 MiB range.
Is the default hugetlb size is larger, mmap() will fail because the
range is not suitable. If the default hugetlb size is smaller (e.g.,
s390x), mmap() will f
Am 9/26/2024 um 8:16 AM schrieb Mathieu Desnoyers:
On 2024-09-25 15:20, Mathieu Desnoyers wrote:
[...]
static inline
bool same_ptr(void *a, void *b)
{
asm goto (
"cmpq %[a], %[b]\n\t"
"jne %l[ne]\n\t"
: : [a] "r" (a), [b] "r" (b)
: : ne);
return t
Let's improve the test output. For example, print the proper test
result. Install a SIGBUS handler to catch any SIGBUS instead of
crashing the test on failure.
With unsuitable hugetlb page count:
$ ./hugetlb_fault_after_madv
TAP version 13
1..1
# [INFO] detected default hugetlb page size:
Mario brought to my attention that the hugetlb_fault_after_madv test
is currently always skipped on s390x.
Let's adjust the test to be independent of the default hugetlb page size
and while at it, also improve the test output.
Cc: Andrew Morton
Cc: Shuah Khan
Cc: Mario Casquero
Cc: Breno Leita
We currently assume that the hugetlb page size is 2 MiB, which is
why we mmap() a 2 MiB range.
Is the default hugetlb size is larger, mmap() will fail because the
range is not suitable. If the default hugetlb size is smaller (e.g.,
s390x), mmap() will fail because we would need more than one huget
On 9/26/24 12:57 AM, Shen Lichuan wrote:
> Fixed some confusing typos that were currently identified with codespell,
> the details are as follows:
>
> -in the code comments:
> drivers/nvdimm/nd_virtio.c:100: repsonse ==> response
> drivers/nvdimm/pfn_devs.c:542: namepace ==> namespace
> drivers
On 6/09/24 16:00, Adrian Hunter wrote:
> Hi
>
> There is a long-standing problem whereby running Intel PT on host and guest
> in Host/Guest mode, causes VM-Entry failure.
>
> The motivation for this patch set is to provide a fix for stable kernels
> prior to the advent of the "Mediated Passthroug
On 9/25/24 14:56, Hyeonggon Yoo wrote:
> On Sun, Sep 22, 2024 at 11:13 PM Guenter Roeck wrote:
>>
>> On 9/21/24 23:16, Hyeonggon Yoo wrote:
>> > On Sun, Sep 22, 2024 at 6:25 AM Vlastimil Babka wrote:
>> >>
>> >> On 9/21/24 23:08, Guenter Roeck wrote:
>> >>> On 9/21/24 13:40, Vlastimil Babka wrote
Le 26/09/2024 à 01:38, Matthew Maurer a écrit :
Adds a new format for MODVERSIONS which stores each field in a separate
ELF section. This initially adds support for variable length names, but
could later be used to add additional fields to MODVERSIONS in a
backwards compatible way if needed. A
> On Sep 25, 2024, at 21:08, Marcos Paulo de Souza wrote:
>
> On Wed, 2024-09-25 at 14:40 +0800, Wardenjohn wrote:
>> As previous discussion, maintainers think that patch-level sysfs
>> interface is the
>> only acceptable way to maintain the information of the order that
>> klp_patch is
>> app
On Thu, 2024-09-26 at 11:22 +0200, Paolo Abeni wrote:
>
> Please have a better run at checkpatch before your next submission,
> there are still a few ones - most relevant white-space damage.
Oops, apparently I missed one. Sorry about that.
I'll also add a MAINTAINERS entry, just to make checkpa
Hi Martin,
On 9/25/24 22:01, Martin KaFai Lau wrote:
> On 9/25/24 3:37 AM, Martin KaFai Lau wrote:
>> I am not sure which case in xdp_features.c does not have existing coverage in
>> test_progs. From a quick look, it seems only BPF_MAP_TYPE_CPUMAP is missing
>> (please check)?
>
> Re: CPUMAP, I n
On 26/09/2024 11:32, Paolo Abeni wrote:
> On 9/25/24 18:41, Shuah Khan wrote:
>> On 9/25/24 06:23, Javier Carrasco wrote:
>>> These executables are missing from their corresponding gitignore files.
>>> Add them to the lists.
>>>
>>> Signed-off-by: Javier Carrasco
>>> ---
>>> tools/testing/selft
On 9/25/24 18:41, Shuah Khan wrote:
On 9/25/24 06:23, Javier Carrasco wrote:
These executables are missing from their corresponding gitignore files.
Add them to the lists.
Signed-off-by: Javier Carrasco
---
tools/testing/selftests/core/.gitignore | 1 +
tools/testing/selftests/net/.gitign
On 9/20/24 11:32, David Woodhouse wrote:
From: David Woodhouse
The vmclock device addresses the problem of live migration with
precision clocks. The tolerances of a hardware counter (e.g. TSC) are
typically around ±50PPM. A guest will use NTP/PTP/PPS to discipline that
counter against an extern
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni :
On Thu, 19 Sep 2024 16:13:51 +0800 you wrote:
> Currently, the virtio-net driver will perform a pre-dma-mapping for
> small or mergeable RX buffer. But for small packets, a mismatched address
> without VIRTNET_RX_PAD and xdp_
On 2024/8/28 00:59, Nicolin Chen wrote:
Now a VIOMMU can wrap a shareable nested parent HWPT. So, it can act like
a nested parent HWPT to allocate a nested HWPT.
Support that in the IOMMU_HWPT_ALLOC ioctl handler, and update its kdoc.
Also, associate a viommu to an allocating nested HWPT.
it
On 2024/9/26 02:55, Nicolin Chen wrote:
On Wed, Sep 25, 2024 at 06:30:20PM +0800, Yi Liu wrote:
Hi Nic,
On 2024/8/28 00:59, Nicolin Chen wrote:
This series introduces a new VIOMMU infrastructure and related ioctls.
IOMMUFD has been using the HWPT infrastructure for all cases, including a
nest
Fixed some confusing typos that were currently identified with codespell,
the details are as follows:
-in the code comments:
drivers/nvdimm/nd_virtio.c:100: repsonse ==> response
drivers/nvdimm/pfn_devs.c:542: namepace ==> namespace
drivers/nvdimm/pmem.c:319: reenable ==> re-enable
Signed-off-by:
On Wed, Sep 25, 2024 at 11:22:40PM -0400, Shaoqin Huang wrote:
> Currently FEAT_RAS is not writable, this makes migration fail between
> systems where this feature differ. Allow the FEAT_RAS writable in
> ID_AA64PFR0_EL1 to let the migration possible when the RAS is differ
> between two machines.
>
80 matches
Mail list logo
