From: Avi Kivity <avi@redhat.com>
To: Nico Prenzel <nico.prenzel@pn-systeme.de>
Cc: kvm@vger.kernel.org
Subject: Re: Antwort: Re: Passthrough VIA CPU Features
Date: Mon, 27 Dec 2010 16:18:39 +0200 [thread overview]
Message-ID: <4D18A03F.2020309@redhat.com> (raw)
In-Reply-To: <OFED7420D2.349AEB14-ONC1257806.004D7311-C1257806.004D7314@pn-systeme.de>
On 12/27/2010 04:05 PM, Nico Prenzel wrote:
> Hello Avi,
>
> thanks for your quick respone. That doesn't sound bad!
> I've found the needed documentation (I think):
> http://www.via.com.tw/en/downloads/whitepapers/initiatives/padlock/programming_guide.pdf
>
> As my C knowloedge isn't hardware related, i don't understand what to look for. Of course, I'll read through it to gather some informations.
> But I don't think I'll finish... Pherhaps someone could grab this and implements the needed changes.
Often, the processor vendors implement vendor specific features. That's
certainly the usual case with kvm. Try contacting Via.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-27 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 12:37 Passthrough VIA CPU Features Nico Prenzel
2010-12-27 12:54 ` Avi Kivity
2010-12-27 14:05 ` Antwort: " Nico Prenzel
2010-12-27 14:18 ` Avi Kivity [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=4D18A03F.2020309@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nico.prenzel@pn-systeme.de \
/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