From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: pbonzini@redhat.com, imammedo@redhat.com, gleb@kernel.org,
mtosatti@redhat.com, stefanha@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, dan.j.williams@intel.com,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v5 5/5] nvdimm acpi: add _CRS
Date: Thu, 3 Mar 2016 22:05:31 +0800 [thread overview]
Message-ID: <56D844AB.5060805@linux.intel.com> (raw)
In-Reply-To: <20160303152819-mutt-send-email-mst@redhat.com>
On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
> On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
>> As Igor suggested that we can report the BIOS patched operation region
>> so that OSPM could see that particular range is in use and be able to
>> notice conflicts if it happens some day
>>
>> Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
>
> This is reserved RAM, exposing it in _CRS makes no sense to me.
As more and more memory will be reserved by BIOS/QEMU, report the
information to OSPM and let it check the potential error is bad,
no? :)
WARNING: multiple messages have this Message-ID (diff)
From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, gleb@kernel.org,
mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
imammedo@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: Thu, 3 Mar 2016 22:05:31 +0800 [thread overview]
Message-ID: <56D844AB.5060805@linux.intel.com> (raw)
In-Reply-To: <20160303152819-mutt-send-email-mst@redhat.com>
On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
> On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
>> As Igor suggested that we can report the BIOS patched operation region
>> so that OSPM could see that particular range is in use and be able to
>> notice conflicts if it happens some day
>>
>> Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
>
> This is reserved RAM, exposing it in _CRS makes no sense to me.
As more and more memory will be reserved by BIOS/QEMU, report the
information to OSPM and let it check the potential error is bad,
no? :)
next prev parent reply other threads:[~2016-03-03 14:05 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 11:50 [PATCH v5 0/5] NVDIMM ACPI: introduce the framework of QEMU emulated DSM Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:50 ` [PATCH v5 1/5] nvdimm acpi: initialize the resource used by NVDIMM ACPI Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:58 ` Michael S. Tsirkin
2016-03-02 11:58 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-02 16:10 ` Xiao Guangrong
2016-03-02 16:10 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:50 ` [PATCH v5 2/5] nvdimm acpi: introduce patched dsm memory Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-03 13:12 ` Michael S. Tsirkin
2016-03-03 13:12 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-03 13:35 ` Xiao Guangrong
2016-03-03 13:35 ` [Qemu-devel] " Xiao Guangrong
2016-03-04 15:32 ` Xiao Guangrong
2016-03-04 15:32 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:50 ` [PATCH v5 3/5] nvdimm acpi: let qemu handle _DSM method Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-03 13:23 ` Michael S. Tsirkin
2016-03-03 13:23 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-03 14:00 ` Xiao Guangrong
2016-03-03 14:00 ` [Qemu-devel] " Xiao Guangrong
2016-03-04 15:03 ` Xiao Guangrong
2016-03-04 15:03 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:50 ` [PATCH v5 4/5] nvdimm acpi: emulate dsm method Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-03 13:25 ` Michael S. Tsirkin
2016-03-03 13:25 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-03 14:01 ` Xiao Guangrong
2016-03-03 14:01 ` [Qemu-devel] " Xiao Guangrong
2016-03-02 11:50 ` [PATCH v5 5/5] nvdimm acpi: add _CRS Xiao Guangrong
2016-03-02 11:50 ` [Qemu-devel] " Xiao Guangrong
2016-03-03 13:29 ` Michael S. Tsirkin
2016-03-03 13:29 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-03 14:05 ` Xiao Guangrong [this message]
2016-03-03 14:05 ` Xiao Guangrong
2016-03-03 14:48 ` Michael S. Tsirkin
2016-03-03 14:48 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-07 12:16 ` Igor Mammedov
2016-03-07 12:16 ` [Qemu-devel] " Igor Mammedov
2016-03-07 12:22 ` Michael S. Tsirkin
2016-03-07 12:22 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-07 14:49 ` Igor Mammedov
2016-03-07 14:49 ` [Qemu-devel] " Igor Mammedov
2016-03-07 15:09 ` Michael S. Tsirkin
2016-03-07 15:09 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-07 16:17 ` Igor Mammedov
2016-03-07 16:17 ` [Qemu-devel] " Igor Mammedov
2016-03-07 16:19 ` Michael S. Tsirkin
2016-03-07 16:19 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-08 9:06 ` Igor Mammedov
2016-03-03 13:43 ` [PATCH v5 0/5] NVDIMM ACPI: introduce the framework of QEMU emulated DSM Michael S. Tsirkin
2016-03-03 13:43 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-03 14:07 ` Xiao Guangrong
2016-03-03 14:07 ` [Qemu-devel] " 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=56D844AB.5060805@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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 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.