From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] QEMU e820 reservation patch
Date: Mon, 22 Feb 2010 11:23:49 +0200 [thread overview]
Message-ID: <4B824D25.1020003@redhat.com> (raw)
In-Reply-To: <20100221191351.GA30303@morn.localdomain>
On 02/21/2010 09:13 PM, Kevin O'Connor wrote:
>
>> 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.
>>
> What parts of the memory map do you envision qemu managing?
>
Not a lot. SeaBIOS should manage hardware devices memory requirements,
as it does with PCI and HPET. That leaves non-hardware memory
requirements. The kvm reserved areas fall into this category, but I
don't think there are others.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-22 9:24 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
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 [this message]
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=4B824D25.1020003@redhat.com \
--to=avi@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--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).