search for: mmus

...and the > pte entry checked to be sure it is still pte_none/is_zero_pfn(). If not, > the new page isn't inserted. If it is still none/zero, the new device private > struct page is inserted into the page table, replacing the pte_none()/is_zero_pfn() > page table entry. The secondary MMUs were already invalidated in the migrate_vma_setup() > step and a pte_none() or zero page can't be modified so the only invalidation needed > is the CPU TLB(s) for clearing the special zero page PTE entry. No, the secondary MMU was invalidated but the invalidation start/end range was exit...

And, one more weird thing in this function. The FILESize static variable is never initialized so its likely initial value is 0 due to zero fill on many MMUs. The value is never written and used as a divisor. Why hasn't this function caused an arithmetic violation? Because the IOBBase point, also a static variable is initialized to zero and never modified and used in a conditional that thwarts the second if statement. This function amounts to a hug...

On Thu, Jul 23, 2020 at 03:30:04PM -0700, Ralph Campbell wrote: > When migrating the special zero page, migrate_vma_pages() calls > mmu_notifier_invalidate_range_start() before replacing the zero page > PFN in the CPU page tables. This is unnecessary since the range was > invalidated in migrate_vma_setup() and the page table entry is checked > to be sure it hasn't changed

...oo long to complete. It would probably be acceptable to XFAIL them when run with a software memory manager enabled and then consider ways to adopt them as necessary on a per-test basis. * * * With this paper we propose the changes that make it possible to use sanitizers on plaforms that have no MMUs to be part of the mainline. However, before moving further we would like some feedback from the community so comments are very appreciated. If the approach is fine, we will prepare a set of patches shortly. Thank you, -- -------------- next part -------------- A non-text attachment was scrubb...

...page table is locked and the pte entry checked to be sure it is still pte_none/is_zero_pfn(). If not, the new page isn't inserted. If it is still none/zero, the new device private struct page is inserted into the page table, replacing the pte_none()/is_zero_pfn() page table entry. The secondary MMUs were already invalidated in the migrate_vma_setup() step and a pte_none() or zero page can't be modified so the only invalidation needed is the CPU TLB(s) for clearing the special zero page PTE entry. Two devices could both try to do the migrate_vma_*() sequence and proceed in parallel up to t...

...nel, and you'll see better performance (and memory will be limited to 960MiB). In a nutshell, you should be running Linux/x86-64 on systems with more than 1GiB for optimal performance. If you have more than 4GiB of combined system and memory mapped I/O, you should be running Opterons with I/O MMUs. Intel EM64T systems will have protections in place for both earlier generation GTL+ limitations, as well as lack of an I/O MMU. Much of the additional "tangent" surrounded the fact that there are a few so-called "32-bit" Athlons that actually have a BIOS hack and Linux kernel...

Given that the Document Foundation has now split away from Oracle to continue the development of an independent office suite, do we have any idea which was CentOS and Red Hat are planning to go in this area - OpenOffice or LibreOffice? I know that LibreOffice is not production ready yet - they only have their first beta available, but it's just a matter of (likely a short) time before the

...am fixated on that??? http://lists.centos.org/pipermail/centos/2005-June/007341.html "<even more anal>Except the iommu, those are limitations of chipset, bus and whatever, not EM64T.</even more anal>" It very much has to do with how EM64T differs from AMD64. GARTs and I/O MMUs are even more capable than the Opteron. The issue has not yet been forced on Intel _because_ they still use a "single point of contention" design. All CPUs share one bus, all memory shares another, etc... into a "hub" (with exception of a proprietary NUMA solution, but all I/O...

I mis-stated what I think should be deleted. The block of code from "GlobalVariable *IOB = 0;" to the end of the loop should be delted because the only effect the loop has is on the IOB variable and that variable is never used after the loop. Reid. On Tue, 2004-05-11 at 18:14, Reid Spencer wrote: > Hi, > > I'm working on bug 122, consolidating the interface to the

Hi, I'm working on bug 122, consolidating the interface to the SymbolTable class. In doing so, I found the function below which traverses the symbol table but apparently unnecessarily. Before I remove the traversal, I thought I better check with you guys. Posted this to the list because it looks like _everyone_ has edited this file :) In the code below, the IOB variable is the only thing in

...is's will release a firmware upgrade "soon" for the SP600 portable music player, allowing it to play Vorbis files. NOTES: http://www.pontis.de/site_e/produkte/pl_600_e.htm iPod Having nothing to do with apple, some people have uClinux (Linux for CPU's without MMUs) running on this. Right now, they are decoding Oggs at .8x, with hope for improvement. http://ipodlinux.sourceforge.net/ iRiver Xiph.org is working with prototypes from iRiver to create a (new, right?) portable music player which can play Ogg Vorbis. Development is conti...

This series adds new functions to the mmu interval notifier API to allow device drivers with MMUs to dynamically mirror a process' page tables based on device faults and invalidation callbacks. The Nouveau driver is updated to use the extended API and a set of stand alone self tests is added to help validate and maintain correctness. The patches are based on linux-5.5.0-rc6 and are for Jas...

This patch series is based on the VM introspection patches (https://lore.kernel.org/kvm/20200721210922.7646-1-alazar at bitdefender.com/), extending the introspection API with EPT Views and Virtualization Exceptions (#VE) support. The purpose of this series is to get an initial feedback and to see if we are on the right track, especially because the changes made to add the EPT views are not small