From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] Qemu: Add sanity check for vcpu config
Date: Tue, 23 Mar 2010 07:22:13 +0000 [thread overview]
Message-ID: <C7CE1CA5.E28D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A384659F19E@shzsmsx502.ccr.corp.intel.com>
I'm not dead against a sanity check in qemu.
-- Keir
On 23/03/2010 02:17, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
> Keir,
>
> Have you decided where should vcpu sanity check be located?
> We add vcpu sanity check at qemu because:
> 1. xen/qemu itself has knowledge like HVM_MAX_VCPUS, xend doesn't have such
> knowledge;
> 2. there are many ways to transfer config/cmdline para to qemu, xm/xend is one
> of them which used at Xen. On other system like KVM, there is no xm/xend at
> all. So naturely qemu is a better place to do sanity check than xend;
> 3. even if we add sanity check at xend, qemu still need do sanity check. After
> all, qemu cannot totally trust its input;
>
> Thanks,
> Jinsong
>
> Ian Jackson wrote:
>> Keir Fraser writes ("[Xen-devel] Re: [PATCH] Qemu: Add sanity check
>> for vcpu config"):
>>> Wouldn't xend be a more sensible place to do the check? It can
>>> certainly result in a better error message, I would have thought.
>>
>> Quite so. If you add feature to xend, it should be changed in libxl
>> too.
>>
>> Ian.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-03-23 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 15:09 [PATCH] Qemu: Add sanity check for vcpu config Liu, Jinsong
2010-03-21 17:15 ` Keir Fraser
2010-03-22 17:21 ` Ian Jackson
2010-03-23 2:17 ` Liu, Jinsong
2010-03-23 7:22 ` Keir Fraser [this message]
2010-03-23 8:07 ` Liu, Jinsong
2010-03-24 11:20 ` Ian Jackson
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=C7CE1CA5.E28D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jinsong.liu@intel.com \
--cc=xen-devel@lists.xensource.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).