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@xen.org>
Subject: Re: [PATCH 2/2] hvm: allow pass-through of new CPUID features
Date: Thu, 27 Jan 2011 13:05:19 +0100 [thread overview]
Message-ID: <4D415F7F.3050206@amd.com> (raw)
In-Reply-To: <19776.18018.384751.824459@mariner.uk.xensource.com>
Ian Jackson wrote:
> Andre Przywara writes ("[Xen-devel] [PATCH 2/2] hvm: allow pass-through of new CPUID features"):
>> there are some new CPUID features that are safe for guests to see, as
>> they don't require OS awareness (FPU/ALU related instructions only).
>> Among features for new AMD CPUs there is also the PCLMULQDQ bit, which
>> Intel CPU have already for quite a while.
>
> This would seem to be a new feature.
I agree to some point, although (at least in respect to PCLMULQDQ) I'd
consider this more as "forgotten enablement".
> We are currently in feature freeze.
>
> Can you make a justification for a freeze exception ?
If you can make me believe that it does not take another year until this
shows up in an official release, then I am totally fine with skipping 4.1.0.
What is the policy regarding the 4.1.x releases? Have features like
those a chance of being applied?
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
next prev parent reply other threads:[~2011-01-27 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 14:04 [PATCH 2/2] hvm: allow pass-through of new CPUID features Andre Przywara
2011-01-26 16:05 ` Ian Jackson
2011-01-27 12:05 ` Andre Przywara [this message]
2011-01-27 12:13 ` Stefano Stabellini
2011-01-27 14:53 ` Ian Jackson
2011-01-27 15:43 ` Andre Przywara
2011-01-27 15:56 ` Andre Przywara
2011-01-27 19:50 ` Ian Jackson
2011-01-27 16:07 ` Keir Fraser
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=4D415F7F.3050206@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir@xen.org \
--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.