Currently the virtio_ring structure are not declared packed, but they
describe an hardware like interface. We should not allow compilers to make
alignments and optimizations that can be different between the guest and
host compiler.
I propose to declare all structures that are in shared memory
This patch seems reasonable to me.
But FWIW, with extboot, it's possible to implement the -kernel option in
a saner way. extboot already has code to take over int19 and load a
kernel from memory on boot. It was based on the old -kernel support in
QEMU (prior to hpa's rewrite) so it's not
Two callbacks to remove individual pages as done in rmap code
invalidate_page()
Called from the inner loop of rmap walks to invalidate pages.
age_page()
Called for the determination of the page referenced status.
If we do not care about page referenced status then an age_page
The invalidation of address ranges in a mm_struct needs to be
performed when pages are removed or permissions etc change.
If invalidate_range_begin() is called with locks held then we
pass a flag into invalidate_range() to indicate that no sleeping is
possible. Locks are only held for truncate
On Fri, Feb 08, 2008 at 03:32:19PM -0800, Christoph Lameter wrote:
On Fri, 8 Feb 2008, Andrew Morton wrote:
What about ib_umem_get()?
Ok. It pins using an elevated refcount. Same as XPmem right now. With that
we effectively pin a page (page migration will fail) but we will
continually
On Fri, 8 Feb 2008, Robin Holt wrote:
What about ib_umem_get()?
Ok. It pins using an elevated refcount. Same as XPmem right now. With that
we effectively pin a page (page migration will fail) but we will
continually be reclaiming the page and may repeatedly try to move it. We
On Fri, 08 Feb 2008 14:06:16 -0800
Christoph Lameter [EMAIL PROTECTED] wrote:
This is a patchset implementing MMU notifier callbacks based on Andrea's
earlier work. These are needed if Linux pages are referenced from something
else than tracked by the rmaps of the kernel (an external MMU). MMU
Stephen Hemminger wrote:
I notice that recent KVM is incompatiable with older versions.
Using a KVM image created on 2.6.24 will crash on 2.6.25 (or
vice versa). It appears that Ubuntu Hardy has incorporated the 2.6.25
update even though it claims to be 2.6.24.
This isn't intentional.
On Fri, 8 Feb 2008 17:43:02 -0600 Robin Holt [EMAIL PROTECTED] wrote:
On Fri, Feb 08, 2008 at 03:41:24PM -0800, Christoph Lameter wrote:
On Fri, 8 Feb 2008, Robin Holt wrote:
What about ib_umem_get()?
Correct.
You missed the turn of the conversation to how ib_umem_get()
These special additional callbacks are required because XPmem (and likely
other mechanisms) do use their own rmap (multiple processes on a series
of remote Linux instances may be accessing the memory of a process).
F.e. XPmem may have to send out notifications to remote Linux instances
and receive
On Fri, Feb 08, 2008 at 03:41:24PM -0800, Christoph Lameter wrote:
On Fri, 8 Feb 2008, Robin Holt wrote:
What about ib_umem_get()?
Correct.
You missed the turn of the conversation to how ib_umem_get() works.
Currently it seems to pin the same way that the SLES10 XPmem works.
Ah. I
On Fri, 8 Feb 2008, Roland Dreier wrote:
In general, this MMU notifier stuff will only be useful to a subset of
InfiniBand/RDMA hardware. Some adapters are smart enough to handle
changing the IO virtual - bus/physical mapping on the fly, but some
aren't. For the dumb adapters, I think the
On Fri, 8 Feb 2008, Andrew Morton wrote:
Quite possibly none of the infiniband developers even know about it..
Well Andrea's initial approach was even featured on LWN a couple of
weeks back.
-
This SF.net email is
unsubscribe
Date: Fri, 8 Feb 2008 16:16:34 -0800 From: [EMAIL PROTECTED] To: [EMAIL
PROTECTED] CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; kvm-devel@lists.sourceforge.net; [EMAIL
I thought the adaptor can always remove the mapping by renegotiating
with the remote side? Even if its dumb then a callback could notify the
driver that it may be required to tear down the mapping. We then hold the
pages until we get okay by the driver that the mapping has been removed.
On Fri, 8 Feb 2008 16:05:00 -0800 (PST) Christoph Lameter [EMAIL PROTECTED]
wrote:
On Fri, 8 Feb 2008, Andrew Morton wrote:
You took it correctly, and I didn't understand the answer ;)
We have done several rounds of discussion on linux-kernel about this so
far and the IB folks have not
On Fri, 08 Feb 2008 16:22:12 -0600
Anthony Liguori [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
I notice that recent KVM is incompatiable with older versions.
Using a KVM image created on 2.6.24 will crash on 2.6.25 (or
vice versa). It appears that Ubuntu Hardy has incorporated the
On Fri, 8 Feb 2008, Andrew Morton wrote:
You took it correctly, and I didn't understand the answer ;)
We have done several rounds of discussion on linux-kernel about this so
far and the IB folks have not shown up to join in. I have tried to make
this as general as possible.
We have done several rounds of discussion on linux-kernel about this so
far and the IB folks have not shown up to join in. I have tried to make
this as general as possible.
Sorry, this has been on my things to look at list for a while, but I
haven't gotten a chance to really understand
On Fri, 8 Feb 2008, Roland Dreier wrote:
That would of course work -- dumb adapters would just always fail,
which might be inefficient.
H.. that means we need something that actually pins pages for good so
that the VM can avoid reclaiming it and so that page migration can avoid
trying to
On Fri, Feb 08, 2008 at 04:36:16PM -0800, Christoph Lameter wrote:
On Fri, 8 Feb 2008, Roland Dreier wrote:
That would of course work -- dumb adapters would just always fail,
which might be inefficient.
H.. that means we need something that actually pins pages for good so
that the
On Fri, Feb 08, 2008 at 05:27:03PM -0800, Christoph Lameter wrote:
Pages will still be on the LRU and cycle through rmap again and again.
If page migration is used on those pages then the code may make repeated
attempt to migrate the page thinking that the page count must at some
point
On Sat, 9 Feb 2008, Andrea Arcangeli wrote:
The VM shouldn't break if try_to_unmap doesn't actually make the page
freeable for whatever reason. Permanent pins shouldn't happen anyway,
VM is livelocking if too many page are pinned that way right now. The
higher the processors per node the
23 matches
Mail list logo
