From: Rusty Russell <rusty@rustcorp.com.au>
To: lguest@ozlabs.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Roel Kluin <roel.kluin@gmail.com>,
Matias Zabaljauregui <zabaljauregui@gmail.com>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Lguest] [PULL] lguest and virtio patches
Date: Sun, 29 Mar 2009 00:24:22 +1030 [thread overview]
Message-ID: <200903290024.23218.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200903282341.54810.rusty@rustcorp.com.au>
On Saturday 28 March 2009 23:41:54 Rusty Russell wrote:
> The following changes since commit 5d80f8e5a9dc9c9a94d4aeaa567e219a808b8a4a:
...
> lguest: avoid accidental recycling of pgdir pages
Actually, I've repushed without this change: Jeremy convinced me it's not
necessary.
If you pulled in between, it's no big deal.
Rusty.
New stats:
Matias Zabaljauregui (2):
lguest: use KVM hypercalls
lguest: use bool instead of int
Roel Kluin (1):
virtio: fix BAD_RING, START_US and END_USE macros
Rusty Russell (4):
virtio: more neatening of virtio_ring macros.
lguest: fix spurious BUG_ON() on invalid guest stack.
lguest: wire up pte_update/pte_update_defer
lguest: barrier me harder
Documentation/lguest/lguest.c | 7 +++
arch/x86/include/asm/lguest_hcall.h | 24 ++--------
arch/x86/lguest/boot.c | 86 ++++++++++++++++++++++-----------
arch/x86/lguest/i386_head.S | 4 +-
drivers/lguest/core.c | 4 +-
drivers/lguest/interrupts_and_traps.c | 28 ++++++-----
drivers/lguest/lg.h | 8 ++--
drivers/lguest/lguest_device.c | 4 +-
drivers/lguest/page_tables.c | 22 +++++----
drivers/lguest/segments.c | 2 +-
drivers/lguest/x86/core.c | 62 +++++++++++++++++++++++-
drivers/virtio/virtio_ring.c | 22 +++++---
12 files changed, 181 insertions(+), 92 deletions(-)
prev parent reply other threads:[~2009-03-28 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 13:11 [PULL] lguest and virtio patches Rusty Russell
2009-03-28 13:54 ` Rusty Russell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903290024.23218.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=zabaljauregui@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.