search for: poppling

Device exclusive page table entries are used to prevent CPU access to a page whilst it is being accessed from a device. Typically this is used to implement atomic operations when the underlying bus does not support atomic access. When a CPU thread encounters a device exclusive entry it locks the page and restores the original entry after calling mmu notifiers to signal drivers that exclusive

Hi, Jean, thanks for your source code example. I like ask info about cpu consuption, in our example enabling echo removing cause the sound poppling with a celeron 1.7Ghz (taskman show cpu full, without echo is at 30%). Does exist a mode to lower the cpu consuption in echo removing? Because a large part of users base own still "old" CPU of 6-7 generation, as from 500-700 Mhz and lower too. Perhaps the code need be optimized? Or can...

Device exclusive page table entries are used to prevent CPU access to a page whilst it is being accessed from a device. Typically this is used to implement atomic operations when the underlying bus does not support atomic access. When a CPU thread encounters a device exclusive entry it locks the page and restores the original entry after calling mmu notifiers to signal drivers that exclusive

The quilt patch titled Subject: locking/ww_mutex/test: add MODULE_DESCRIPTION() has been removed from the -mm tree. Its filename was locking-ww_mutex-test-add-module_description.patch This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Jeff

The quilt patch titled Subject: x86/mm: add testmmiotrace MODULE_DESCRIPTION() has been removed from the -mm tree. Its filename was x86-mm-add-testmmiotrace-module_description.patch This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm ------------------------------------------------------ From: Jeff

This is an initial series of patches to improve channel recovery on Turing GPUs with the goal of improving reliability enough to eventually enable SVM for Turing. It's likely follow up patches will be required to fully address problems with less trivial workloads than what I have been able to test thus far. This series primarily addresses a number of hardware changes to interrupt layout and

The quilt patch titled Subject: crypto: arm/xor - add missing MODULE_DESCRIPTION() macro has been removed from the -mm tree. Its filename was crypto-arm-xor-add-missing-module_description-macro.patch This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

The patch titled Subject: locking/ww_mutex/test: add MODULE_DESCRIPTION() has been added to the -mm mm-nonmm-unstable branch. Its filename is locking-ww_mutex-test-add-module_description.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/locking-ww_mutex-test-add-module_description.patch This patch will later

The patch titled Subject: x86/mm: add testmmiotrace MODULE_DESCRIPTION() has been added to the -mm mm-nonmm-unstable branch. Its filename is x86-mm-add-testmmiotrace-module_description.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/x86-mm-add-testmmiotrace-module_description.patch This patch will later appear

On 3/27/23 19:14, Alistair Popple wrote: > Device exclusive page table entries are used to prevent CPU access to > a page whilst it is being accessed from a device. Typically this is > used to implement atomic operations when the underlying bus does not > support atomic access. When a CPU thread encounters a device exclusive > entry it locks the page and restores the original entry

The quilt patch titled Subject: cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros has been removed from the -mm tree. Its filename was cpufreq-powerpc-add-missing-module_description-macros.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Jeff Johnson <quic_jjohnson at

The patch titled Subject: crypto: arm/xor - add missing MODULE_DESCRIPTION() macro has been added to the -mm mm-nonmm-unstable branch. Its filename is crypto-arm-xor-add-missing-module_description-macro.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/crypto-arm-xor-add-missing-module_description-macro.patch This

The quilt patch titled Subject: fsi: add missing MODULE_DESCRIPTION() macros has been removed from the -mm tree. Its filename was fsi-add-missing-module_description-macros.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Jeff Johnson <quic_jjohnson at quicinc.com> Subject: fsi: add

The patch titled Subject: cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros has been added to the -mm mm-nonmm-unstable branch. Its filename is cpufreq-powerpc-add-missing-module_description-macros.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/cpufreq-powerpc-add-missing-module_description-macros.patch

The patch titled Subject: fsi: add missing MODULE_DESCRIPTION() macros has been added to the -mm mm-nonmm-unstable branch. Its filename is fsi-add-missing-module_description-macros.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fsi-add-missing-module_description-macros.patch This patch will later appear in the

On Tue, Jan 24, 2023 at 04:42:31PM +1100, Alistair Popple wrote: > diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c > index ec32f78..a31dd53 100644 > --- a/drivers/vhost/vdpa.c > +++ b/drivers/vhost/vdpa.c ... > @@ -780,6 +780,10 @@ static int vhost_vdpa_map(struct vhost_vdpa *v, struct vhost_iotlb *iotlb, > u32 asid = iotlb_to_asid(iotlb); > int r = 0; >

On Tue, Mar 28, 2023 at 01:14:34PM +1100, Alistair Popple wrote: > +++ b/mm/memory.c > @@ -3623,8 +3623,19 @@ static vm_fault_t remove_device_exclusive_entry(struct vm_fault *vmf) > struct vm_area_struct *vma = vmf->vma; > struct mmu_notifier_range range; > > - if (!folio_lock_or_retry(folio, vma->vm_mm, vmf->flags)) > + /* > + * We need a page reference to

John Hubbard <jhubbard at nvidia.com> writes: > On 3/28/23 20:16, Matthew Wilcox wrote: > ... >>> + if (!get_page_unless_zero(vmf->page)) >>> + return 0; >> From a folio point of view: what the hell are you doing here? Tail >> pages don't have individual refcounts; all the refcounts are actually I had stuck with using the page because none of

Hi, I have got a Powerware 5110 UPS which has a usb interface on it. I have downloaded and compiled nut-2.0.3-pre2 with the usb drivers enabled on RedHat Enterprise V3 however I have been unable to get nut to connect to the UPS. I have tried executing the driver directly (using bcmxcp_usb -DD -u root /proc/bus/usb/002/002) as well as using upsdrvctl with the port set to auto (am I correct in

"Zhou, Xianrong" <Xianrong.Zhou at amd.com> writes: > [AMD Official Use Only - General] > >> >>>>> The vmf_insert_pfn_prot could cause unnecessary double faults on a >> >>>>> device pfn. Because currently the vmf_insert_pfn_prot does not >> >>>>> make the pfn writable so the pte entry is normally read-only or