From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
ehabkost@redhat.com, kvm@vger.kernel.org, gleb@kernel.org,
mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
pbonzini@redhat.com, dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v5 5/5] nvdimm acpi: add _CRS
Date: Mon, 7 Mar 2016 18:19:46 +0200 [thread overview]
Message-ID: <20160307181839-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20160307171719.2cb4f2de@nial.brq.redhat.com>
On Mon, Mar 07, 2016 at 05:17:19PM +0100, Igor Mammedov wrote:
> > > So what would happen when PCI MMIO BAR would be mapped over above range,
> > > since guest thinks it's free to use it as unused resource?
> >
> > IIRC, allocating MMIO BAR over RAM would make the MMIO invisible,
> > irrespective of whether the RAM range is being used for anything.
> An then driver would start writing 'garbage' to RAM, resulting in
> strange guest behavior and not work PCI device.
Do you observe such behaviour?
> that's why reserving region is a good idea if it could be done.
Which region? Reserve all of RAM in _CRS?
> >
> > >
> > > >
> > > > > So we should either reserve range or punch a hole in PCI0._CRS.
> > > > > Reserving ranges is simpler and that's what we've switched to
> > > > > from manual hole punching, see PCI/CPU/Memory hotplug and other
> > > > > motherboard resources.
next prev parent reply other threads:[~2016-03-07 16:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 11:50 [Qemu-devel] [PATCH v5 0/5] NVDIMM ACPI: introduce the framework of QEMU emulated DSM Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] [PATCH v5 1/5] nvdimm acpi: initialize the resource used by NVDIMM ACPI Xiao Guangrong
2016-03-02 11:58 ` Michael S. Tsirkin
2016-03-02 16:10 ` Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] [PATCH v5 2/5] nvdimm acpi: introduce patched dsm memory Xiao Guangrong
2016-03-03 13:12 ` Michael S. Tsirkin
2016-03-03 13:35 ` Xiao Guangrong
2016-03-04 15:32 ` Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] [PATCH v5 3/5] nvdimm acpi: let qemu handle _DSM method Xiao Guangrong
2016-03-03 13:23 ` Michael S. Tsirkin
2016-03-03 14:00 ` Xiao Guangrong
2016-03-04 15:03 ` Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] [PATCH v5 4/5] nvdimm acpi: emulate dsm method Xiao Guangrong
2016-03-03 13:25 ` Michael S. Tsirkin
2016-03-03 14:01 ` Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] [PATCH v5 5/5] nvdimm acpi: add _CRS Xiao Guangrong
2016-03-03 13:29 ` Michael S. Tsirkin
2016-03-03 14:05 ` Xiao Guangrong
2016-03-03 14:48 ` Michael S. Tsirkin
2016-03-07 12:16 ` Igor Mammedov
2016-03-07 12:22 ` Michael S. Tsirkin
2016-03-07 14:49 ` Igor Mammedov
2016-03-07 15:09 ` Michael S. Tsirkin
2016-03-07 16:17 ` Igor Mammedov
2016-03-07 16:19 ` Michael S. Tsirkin [this message]
2016-03-08 9:06 ` Igor Mammedov
2016-03-03 13:43 ` [Qemu-devel] [PATCH v5 0/5] NVDIMM ACPI: introduce the framework of QEMU emulated DSM Michael S. Tsirkin
2016-03-03 14:07 ` Xiao Guangrong
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=20160307181839-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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).