From: Wei Liu <wei.liu2@citrix.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
qemu-devel@nongnu.org, Xen-devel <xen-devel@lists.xenproject.org>,
Igor Mammedov <imammedo@redhat.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: [Qemu-devel] [PATCH RFC] PCMachineState: introduce acpi_build_enabled field
Date: Tue, 1 Nov 2016 16:53:17 +0000 [thread overview]
Message-ID: <20161101165317.GD30231@citrix.com> (raw)
In-Reply-To: <20161101164827.GZ5057@thinpad.lan.raisama.net>
On Tue, Nov 01, 2016 at 02:48:27PM -0200, Eduardo Habkost wrote:
[...]
> > static void pc_machine_set_nvdimm(Object *obj, bool value, Error **errp)
> > {
> > PCMachineState *pcms = PC_MACHINE(obj);
> > @@ -2159,6 +2173,8 @@ static void pc_machine_initfn(Object *obj)
> > pcms->vmport = ON_OFF_AUTO_AUTO;
> > /* nvdimm is disabled on default. */
> > pcms->acpi_nvdimm_state.is_enabled = false;
> > + /* acpi build is enabled by default. */
> > + pcms->acpi_build_enabled = true;
>
> If you set:
> pcms->acpi_build_enabled = PC_MACHINE_GET_CLASS(pcms)->has_acpi_build;
> the default value will be more consistent with the actual results
> (where pc-1.6 and older don't have ACPI build). Then you would
> probably be able to remove the pcmc->has_acpi_build check from
> acpi_setup() and only check pcms->acpi_build_enabled.
>
Thank you for your good advice.
I take it that you're ok with the name of the field and the code in
general? If so I will drop RFC tag in my next submission.
Wei.
WARNING: multiple messages have this Message-ID (diff)
From: Wei Liu <wei.liu2@citrix.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
qemu-devel@nongnu.org, Sander Eikelenboom <linux@eikelenboom.it>,
Igor Mammedov <imammedo@redhat.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH RFC] PCMachineState: introduce acpi_build_enabled field
Date: Tue, 1 Nov 2016 16:53:17 +0000 [thread overview]
Message-ID: <20161101165317.GD30231@citrix.com> (raw)
In-Reply-To: <20161101164827.GZ5057@thinpad.lan.raisama.net>
On Tue, Nov 01, 2016 at 02:48:27PM -0200, Eduardo Habkost wrote:
[...]
> > static void pc_machine_set_nvdimm(Object *obj, bool value, Error **errp)
> > {
> > PCMachineState *pcms = PC_MACHINE(obj);
> > @@ -2159,6 +2173,8 @@ static void pc_machine_initfn(Object *obj)
> > pcms->vmport = ON_OFF_AUTO_AUTO;
> > /* nvdimm is disabled on default. */
> > pcms->acpi_nvdimm_state.is_enabled = false;
> > + /* acpi build is enabled by default. */
> > + pcms->acpi_build_enabled = true;
>
> If you set:
> pcms->acpi_build_enabled = PC_MACHINE_GET_CLASS(pcms)->has_acpi_build;
> the default value will be more consistent with the actual results
> (where pc-1.6 and older don't have ACPI build). Then you would
> probably be able to remove the pcmc->has_acpi_build check from
> acpi_setup() and only check pcms->acpi_build_enabled.
>
Thank you for your good advice.
I take it that you're ok with the name of the field and the code in
general? If so I will drop RFC tag in my next submission.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-01 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 16:43 [Qemu-devel] [PATCH RFC] PCMachineState: introduce acpi_build_enabled field Wei Liu
2016-11-01 16:43 ` Wei Liu
2016-11-01 16:48 ` [Qemu-devel] " Eduardo Habkost
2016-11-01 16:48 ` Eduardo Habkost
2016-11-01 16:53 ` Wei Liu [this message]
2016-11-01 16:53 ` Wei Liu
2016-11-01 16:59 ` [Qemu-devel] " Eduardo Habkost
2016-11-01 16:59 ` Eduardo Habkost
2016-11-01 17:01 ` [Qemu-devel] " Wei Liu
2016-11-01 17:01 ` Wei Liu
2016-11-01 17:02 ` [Qemu-devel] " Eduardo Habkost
2016-11-01 17:02 ` Eduardo Habkost
2016-11-01 17:12 ` [Qemu-devel] " Wei Liu
2016-11-01 17:12 ` Wei Liu
2016-11-01 17:24 ` [Qemu-devel] " Eduardo Habkost
2016-11-01 17:24 ` Eduardo Habkost
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=20161101165317.GD30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=linux@eikelenboom.it \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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.