From: Andre Przywara <andre.przywara@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Re: [PATCH 0/2] [RFC] xl: add cpuid config file option
Date: Wed, 1 Sep 2010 11:01:31 +0200 [thread overview]
Message-ID: <4C7E166B.4010606@amd.com> (raw)
In-Reply-To: <19581.16081.41312.69006@mariner.uk.xensource.com>
Ian Jackson wrote:
> Stefano Stabellini writes ("[Xen-devel] Re: [PATCH 0/2] [RFC] xl: add cpuid config file option"):
>> On Fri, 27 Aug 2010, Andre Przywara wrote:
>>> This first version works for me, I'd like to hear your comments.
>> I like your approach. Ian, what do you think?
>
> I think this is a nice approach. But there didn't seem to be a patch
> attached to your mail ? :-)
>
>> We would still need another parser for backward compatibility
>> though.
>
> Is it possible to distinguish the old xend syntax and so have libxl
> handle either ? I'm not familiar with the xend cpuid syntax.
xm uses a Python list syntax, so this looks different. It is possible to
tell them apart: Currently you can check the return value of
xlu_cfg_get_list() to try the new approach otherwise, but this prints an
ugly warning to the console. So I created a (silent) get_type function
to check it before calling the respective functions.
The prototype works already, I will test and polish and then send out a
second version later.
>
>> Also I think that parse_cpuid belongs to libxl instead of xl.
>
> Yes.
You are right, I have already moved it (in v2).
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
prev parent reply other threads:[~2010-09-01 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 12:56 [PATCH 0/2] [RFC] xl: add cpuid config file option Andre Przywara
2010-08-30 13:21 ` Stefano Stabellini
2010-08-31 17:41 ` Ian Jackson
2010-09-01 9:01 ` Andre Przywara [this message]
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=4C7E166B.4010606@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.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 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.