All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: BrillyWu@viatech.com.cn
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Add CPUID support for VIA CPU
Date: Wed, 13 Apr 2011 11:59:04 +0300	[thread overview]
Message-ID: <4DA565D8.8050504@redhat.com> (raw)
In-Reply-To: <C4F7CD9A92DBFF48AD8779355CD4D7890D792D@exchsg04.s3graphics.com>

On 04/13/2011 06:26 AM, BrillyWu@viatech.com.cn wrote:
> The CPUIDs for Centaur are added, and then  the features of PadLock
> hardware
> engine on VIA CPU, such as "ace", "ace_en" and so on, can be passed into
> the
> kvm guest.
>

Nice to see this.  Please post a link to the documentation describing 
these features.

>
> +	/* cpuid 0xC0000001.edx */
> +	const u32 kvm_supported_word5_x86_features =
> +		F(XSTORE) | F(XSTORE_EN) | F(XCRYPT) | F(XCRYPT_EN) |
> +		F(ACE2) | F(ACE2_EN) | F(PHE) | F(PHE_EN) |
> +		F(PMM) | F(PMM_EN);
> +

Are all of these features save wrt save/restore? (do they all act on 
state in standard registers?)  Do they need any control register bits to 
be active or MSRs to configure?

> @@ -2484,6 +2504,17 @@ static int kvm_dev_ioctl_get_supported_c
>
>   	r = -E2BIG;
>   	if (nent>= cpuid->nent)
> +		goto out_free;
> +
> +	/* Add support for Centaur's CPUID instruction. */
> +	do_cpuid_ent(&cpuid_entries[nent], 0xC0000000, 0,&nent,
> cpuid->nent);

nent overflow check missing here.  Also, should probably skip if not a Via.

> +	limit = cpuid_entries[nent - 1].eax;
> +	for (func = 0xC0000001; func<= limit&&  nent<  cpuid->nent;
> ++func)
> +		do_cpuid_ent(&cpuid_entries[nent], func, 0,
> +			&nent, cpuid->nent);
> +
> +	r = -E2BIG;
> +	if (nent>= cpuid->nent)
>   		goto out_free;
>
>   	do_cpuid_ent(&cpuid_entries[nent], KVM_CPUID_SIGNATURE, 0,
> &nent,

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-04-13  8:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  3:26 [PATCH] KVM: Add CPUID support for VIA CPU BrillyWu
2011-04-13  8:59 ` Avi Kivity [this message]
2011-04-13 11:05   ` BrillyWu
2011-04-13 11:32     ` Avi Kivity
2011-04-14  3:14       ` BrillyWu
2011-04-14  7:48         ` Avi Kivity
2011-04-14  9:54           ` BrillyWu
2011-04-14 10:07             ` Avi Kivity
2011-04-21 10:06               ` BrillyWu
2011-04-24  7:18                 ` Avi Kivity
2011-04-25  5:55                   ` BrillyWu
2011-04-27  8:48                     ` Avi Kivity
2011-04-28  1:27                       ` [PATCH] qemu-kvm: " BrillyWu
2011-04-14  3:59       ` [PATCH v2] KVM: " BrillyWu

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=4DA565D8.8050504@redhat.com \
    --to=avi@redhat.com \
    --cc=BrillyWu@viatech.com.cn \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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.