From: Laszlo Ersek <lersek@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu devel list <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 wave 2 1/3] hw/isa/lpc_ich9: add SMI feature negotiation via fw_cfg
Date: Mon, 16 Jan 2017 21:51:34 +0100 [thread overview]
Message-ID: <9de0640d-fc7f-eb52-9410-77494f29077e@redhat.com> (raw)
In-Reply-To: <20170113143433.282c9a81@nial.brq.redhat.com>
On 01/13/17 14:34, Igor Mammedov wrote:
> On Thu, 12 Jan 2017 19:24:44 +0100
> Laszlo Ersek <lersek@redhat.com> wrote:
>
> [...]
>> +static void smi_features_ok_callback(void *opaque)
>> +{
>> + ICH9LPCState *lpc = opaque;
>> + uint64_t guest_features;
>> +
>> + if (lpc->smi_features_ok) {
>> + /* negotiation already complete, features locked */
>> + return;
>> + }
>> +
>> + memcpy(&guest_features, lpc->smi_guest_features_le, sizeof guest_features);
>> + le64_to_cpus(&guest_features);
>> + if (guest_features & ~lpc->smi_host_features) {
>> + /* guest requests invalid features, leave @features_ok at zero */
>> + return;
>> + }
>> +
>> + /* valid feature subset requested, lock it down, report success */
>> + lpc->smi_negotiated_features = guest_features;
>> + lpc->smi_features_ok = 1;
>> +}
> [...]
>
>> + .fields = (VMStateField[]) {
>> + VMSTATE_UINT8_ARRAY(smi_guest_features_le, ICH9LPCState,
>> + sizeof(uint64_t)),
>> + VMSTATE_UINT8(smi_features_ok, ICH9LPCState),
>> + VMSTATE_UINT64(smi_negotiated_features, ICH9LPCState),
>
> Couldn't smi_negotiated_features be derived from
> smi_guest_features_le on target side?
No, that's something we must expressly not do.
The "guest-features" file remains writeable (and back-readable) to the
guest after feature validation/lockdown (i.e., after selecting
"features-ok"), it just has no effect on QEMU.
And, if the guest rewrites "guest-features" between feature lockdown and
migration, that must have no effect on the target host either. Hence we
must carry forward the negotiated features originally computed on the
source host.
Thanks
Laszlo
>
>
>> + VMSTATE_END_OF_LIST()
>> + }
>> +};
>> +
>> static const VMStateDescription vmstate_ich9_lpc = {
>> .name = "ICH9LPC",
>> .version_id = 1,
>> @@ -683,6 +761,7 @@ static const VMStateDescription vmstate_ich9_lpc = {
>> },
>> .subsections = (const VMStateDescription*[]) {
>> &vmstate_ich9_rst_cnt,
>> + &vmstate_ich9_smi_feat,
>> NULL
>> }
>> };
>
next prev parent reply other threads:[~2017-01-16 20:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:24 [Qemu-devel] [PATCH v6 wave 2 0/3] q35: add negotiable broadcast SMI Laszlo Ersek
2017-01-12 18:24 ` [Qemu-devel] [PATCH v6 wave 2 1/3] hw/isa/lpc_ich9: add SMI feature negotiation via fw_cfg Laszlo Ersek
2017-01-13 10:15 ` Igor Mammedov
2017-01-13 11:24 ` Laszlo Ersek
2017-01-13 13:34 ` Igor Mammedov
2017-01-16 20:51 ` Laszlo Ersek [this message]
2017-01-17 8:42 ` Igor Mammedov
2017-01-12 18:24 ` [Qemu-devel] [PATCH v6 wave 2 2/3] hw/isa/lpc_ich9: add broadcast SMI feature Laszlo Ersek
2017-01-13 13:09 ` Igor Mammedov
2017-01-16 20:46 ` Laszlo Ersek
2017-01-17 11:21 ` Igor Mammedov
2017-01-17 12:06 ` Laszlo Ersek
2017-01-17 13:20 ` Igor Mammedov
2017-01-17 13:46 ` Laszlo Ersek
2017-01-17 14:20 ` Igor Mammedov
2017-01-17 18:53 ` Laszlo Ersek
2017-01-18 10:03 ` Igor Mammedov
2017-01-18 10:19 ` Laszlo Ersek
2017-01-18 10:23 ` Laszlo Ersek
2017-01-18 12:38 ` Igor Mammedov
2017-01-18 15:42 ` Laszlo Ersek
2017-01-18 16:26 ` Igor Mammedov
2017-01-18 17:23 ` Laszlo Ersek
2017-01-18 18:06 ` Igor Mammedov
2017-01-18 19:11 ` Laszlo Ersek
2017-01-12 18:24 ` [Qemu-devel] [PATCH v6 wave 2 3/3] hw/isa/lpc_ich9: negotiate SMI broadcast on pc-q35-2.9+ machine types Laszlo Ersek
2017-01-13 13:36 ` Igor Mammedov
2017-01-18 19:02 ` [Qemu-devel] [PATCH v6 wave 2 0/3] q35: add negotiable broadcast SMI Michael S. Tsirkin
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=9de0640d-fc7f-eb52-9410-77494f29077e@redhat.com \
--to=lersek@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).