From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin O'Connor <kevin@koconnor.net>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] QEMU e820 reservation patch
Date: Sun, 21 Feb 2010 18:44:55 +0100 [thread overview]
Message-ID: <4B817117.1020700@redhat.com> (raw)
In-Reply-To: <4B7EFC74.10209@codemonkey.ws>
On 02/19/10 22:02, Anthony Liguori wrote:
> Acked-by: Anthony Liguori <aliguori@us.ibm.com>
>
> Would be nice to use git-send-email in the future as your attachments
> are often rendered poorly by mail clients.
Just switching over from quilt to git, and still having issues with
git-send-email. It does some things nicely, other things are a pain in
the b**t with it, especially for single patch submissions.
> I noticed that you use this for the TSS page with EPT but you don't use
> this interface for the rest of memory. I'm curious what you think the
> right long term split is? If QEMU is not managing the full e820 table,
> can we reasonable add entries on our own?
I'd like to have QEMU handle more, I picked the TSS page because we
changed the location of that in the past and it was the one that
triggered my patch in the first place. Now we have the infrastructure,
it will be easier to add more.
Cheers,
Jes
next prev parent reply other threads:[~2010-02-21 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 17:33 [Qemu-devel] [PATCH] QEMU e820 reservation patch Jes Sorensen
2010-02-15 18:54 ` [Qemu-devel] " Stefano Stabellini
2010-02-16 8:49 ` Jes Sorensen
2010-02-19 21:02 ` [Qemu-devel] " Anthony Liguori
2010-02-21 17:44 ` Jes Sorensen [this message]
2010-02-21 19:13 ` Kevin O'Connor
2010-02-22 8:33 ` Gleb Natapov
2010-02-23 1:31 ` Kevin O'Connor
2010-02-23 8:22 ` Gleb Natapov
2010-02-23 13:50 ` Anthony Liguori
2010-02-23 14:01 ` Gleb Natapov
2010-02-22 9:23 ` Avi Kivity
2010-02-19 22:00 ` Anthony Liguori
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=4B817117.1020700@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).