From: "Andreas Färber" <afaerber@suse.de>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"JBeulich@suse.com" <JBeulich@suse.com>
Subject: Re: [Qemu-devel] [PATCH v2] piix: define a TOM register to report the base of PCI
Date: Mon, 18 Mar 2013 17:55:31 +0100 [thread overview]
Message-ID: <51474703.4070406@suse.de> (raw)
In-Reply-To: <403610A45A2B5242BD291EDAE8B37D300FFAFF2A@SHSMSX102.ccr.corp.intel.com>
Am 18.03.2013 16:21, schrieb Hao, Xudong:
>> -----Original Message-----
>> From: Michael S. Tsirkin [mailto:mst@redhat.com]
>> Sent: Wednesday, February 27, 2013 6:50 PM
>> To: Hao, Xudong
>> Cc: aliguori@us.ibm.com; qemu-devel@nongnu.org;
>> stefano.stabellini@eu.citrix.com; xen-devel@lists.xen.org; afaerber@suse.de;
>> JBeulich@suse.com; Zhang, Xiantao
>> Subject: Re: [PATCH v2] piix: define a TOM register to report the base of PCI
>>
>> On Mon, Feb 25, 2013 at 02:53:37PM +0800, Xudong Hao wrote:
>>> v2:
>>> * Use "piix: " in the subject rather than "qemu: "
>>> * Define TOM register as one byte
>>> * Define default TOM value instead of hardcode 0xe0000000 in more that one
>> place
>>> * Use API pci_set_byte for pci config access
>>> * Use dev->config instead of the indirect d->dev.config
>>>
>>> Define a TOM(top of memory) register to report the base of PCI memory,
>> update
>>> memory region dynamically. TOM register are defined to one byte in PCI
>> configure
>>> space, because that only upper 4 bit of PCI memory takes effect for Xen, so
>>> it requires bios set TOM with 16M-aligned.
>>>
>>> Signed-off-by: Xudong Hao <xudong.hao@intel.com>
>>> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
>>
>> Could you supply some motivation for this patch?
>>
>
> It's a fix for Xen. Qemu want more information from Xen, copy Stefano's comments:
>
> QEMU needs to know where the end of the guest's RAM is (because there is
> where it allocates the videoram and other stuff), so at least the size
> of the MMIO hole is important.
Could you please reply to Anthony's comment that this information is
already available via fw_cfg interface? hw/fw_cfg.h is designed so that
it can be embedded elsewhere (e.g., in SeaBIOS and OpenBIOS). Reusing
any information available through that interface would seem much easier
than fiddling with reserved registers on emulated hardware.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-03-18 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361775217-3454-1-git-send-email-xudong.hao@intel.com>
2013-02-25 15:38 ` [PATCH v2] piix: define a TOM register to report the base of PCI Ian Campbell
2013-02-25 16:05 ` Stefano Stabellini
[not found] ` <alpine.DEB.2.02.1302251600180.5360@kaball.uk.xensource.com>
2013-02-26 3:32 ` [Qemu-devel] " Hao, Xudong
[not found] ` <403610A45A2B5242BD291EDAE8B37D300FF7C10B@SHSMSX102.ccr.corp.intel.com>
2013-02-26 5:10 ` Zhang, Xiantao
[not found] ` <B6C2EB9186482D47BD0C5A9A483456440343CD1C@SHSMSX101.ccr.corp.intel.com>
2013-02-26 15:43 ` Stefano Stabellini
[not found] ` <alpine.DEB.2.02.1302261540160.5360@kaball.uk.xensource.com>
2013-02-26 15:50 ` Ian Campbell
[not found] ` <1361893836.26546.304.camel@zakaz.uk.xensource.com>
2013-02-26 19:32 ` Anthony Liguori
2013-02-27 9:49 ` Zhang, Xiantao
[not found] ` <B6C2EB9186482D47BD0C5A9A483456440343F776@SHSMSX101.ccr.corp.intel.com>
2013-02-27 11:06 ` Ian Campbell
[not found] ` <1361963213.26546.348.camel@zakaz.uk.xensource.com>
2013-03-18 15:25 ` Hao, Xudong
2013-03-18 15:25 ` Hao, Xudong
2013-02-27 10:50 ` Michael S. Tsirkin
[not found] ` <20130227105024.GB13054@redhat.com>
2013-03-18 15:21 ` [Qemu-devel] " Hao, Xudong
2013-03-18 15:21 ` Hao, Xudong
2013-03-18 16:55 ` [Qemu-devel] " Andreas Färber
2013-03-18 16:55 ` Andreas Färber [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=51474703.4070406@suse.de \
--to=afaerber@suse.de \
--cc=JBeulich@suse.com \
--cc=aliguori@us.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xudong.hao@intel.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.