From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 4/4] x86/PV: enable the emulated PIT
Date: Mon, 18 Jan 2016 10:50:49 +0100 [thread overview]
Message-ID: <569CB579.5030200@citrix.com> (raw)
In-Reply-To: <569CA5CB02000078000C7C43@prv-mh.provo.novell.com>
El 18/01/16 a les 8.43, Jan Beulich ha escrit:
>>>> On 15.01.16 at 18:45, <roger.pau@citrix.com> wrote:
>> Changes since v2:
>> - Change 'if ( (a && b) || (!a && c) )' into 'if ( a ? b : c )'.
>
> Thanks, but after some more thinking about it I'm afraid there are
> a few more aspects to consider here:
>
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86/domain.c
>> @@ -542,8 +542,9 @@ int arch_domain_create(struct domain *d, unsigned int domcr_flags,
>> d->domain_id, config->emulation_flags);
>> return -EINVAL;
>> }
>> - if ( config->emulation_flags != 0 &&
>> - (!is_hvm_domain(d) || config->emulation_flags != XEN_X86_EMU_ALL) )
>> + if ( is_hvm_domain(d) ? (config->emulation_flags != XEN_X86_EMU_ALL &&
>> + config->emulation_flags != 0) :
>> + (config->emulation_flags != XEN_X86_EMU_PIT) )
>> {
>
> For one I think it would be a good idea to allow zero for PV domains,
> and perhaps even default new DomU-s to have the PIT flag clear.
> (Also - indentation.)
This sounds fine to me, but IMHO, it should be done in a separate patch.
This patch just restores previous behaviour for PV guests, then we can
move on from there.
> And then - is all this working as intended for the hwdom != Dom0
> case?
I have to admit I have not tried it, but AFAICT in the hwdom != Dom0
case the set of enabled emulated devices should be the same as a normal
guest, the hardware domain doesn't get any more or less emulated devices
than any other guest ATM.
Roger.
next prev parent reply other threads:[~2016-01-18 9:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 14:59 [PATCH v2 0/4] HVMlite: minor fixes and Dom0 preparatory patches Roger Pau Monne
2016-01-15 14:59 ` [PATCH v2 1/4] xen/elfnotes: check phys_entry against UNSET_ADDR32 Roger Pau Monne
2016-01-19 9:21 ` Wei Liu
2016-01-15 14:59 ` [PATCH v2 2/4] libelf: rewrite symtab/strtab loading for Dom0 Roger Pau Monne
2016-01-15 14:59 ` [PATCH v2 3/4] x86/hvm: don't set the BSP as initialised in hvm_vcpu_initialise Roger Pau Monne
2016-01-15 14:59 ` [PATCH v2 4/4] x86/PV: enable the emulated PIT Roger Pau Monne
2016-01-15 17:08 ` Jan Beulich
2016-01-15 17:45 ` [PATCH v3 " Roger Pau Monne
2016-01-18 7:43 ` Jan Beulich
2016-01-18 9:29 ` Andrew Cooper
2016-01-18 9:44 ` Jan Beulich
2016-01-18 10:41 ` Andrew Cooper
2016-01-18 11:06 ` Jan Beulich
2016-01-18 16:10 ` Andrew Cooper
2016-01-18 16:27 ` Jan Beulich
2016-01-18 16:33 ` Andrew Cooper
2016-01-18 16:44 ` Jan Beulich
2016-01-18 17:58 ` Roger Pau Monné
2016-01-18 18:03 ` Andrew Cooper
2016-01-19 9:24 ` Ian Campbell
2016-01-19 10:09 ` Andrew Cooper
2016-01-19 10:28 ` Ian Campbell
2016-01-19 10:56 ` Andrew Cooper
2016-01-20 11:57 ` Ian Campbell
2016-01-18 9:50 ` Roger Pau Monné [this message]
2016-01-18 10:06 ` Jan Beulich
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=569CB579.5030200@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.