From: "Joerg Roedel" <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
To: "Avi Kivity" <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] SVM: enable LBRV virtualization if available
Date: Mon, 2 Apr 2007 12:01:13 +0200 [thread overview]
Message-ID: <20070402100113.GR6644@amd.com> (raw)
In-Reply-To: <4610CF62.6040204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, Apr 02, 2007 at 12:39:46PM +0300, Avi Kivity wrote:
> Joerg Roedel wrote:
> >Is struct svm_cpu_data a userspace data structure. I ask because in a
> >previous version of the patch the svm_features variable was part of that
> >struct. Thats why I used this type.
> >
>
> No, all userspace stuff is in include/linux/kvm*.h (which uses __u32; uint32_t is for libkvm
> and qemu).
Ok, then the types in that structure should also be fixed :)
Joerg
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-04-02 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 12:21 [PATCH] SVM: enable LBRV virtualization if available Joerg Roedel
[not found] ` <20070330122153.GO6644-5C7GfCeVMHo@public.gmane.org>
2007-03-30 14:04 ` Avi Kivity
[not found] ` <460D18ED.909-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-02 9:32 ` Joerg Roedel
[not found] ` <20070402093256.GQ6644-5C7GfCeVMHo@public.gmane.org>
2007-04-02 9:39 ` Avi Kivity
[not found] ` <4610CF62.6040204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-02 10:01 ` Joerg Roedel [this message]
[not found] ` <20070402100113.GR6644-5C7GfCeVMHo@public.gmane.org>
2007-04-02 10:06 ` Avi Kivity
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=20070402100113.GR6644@amd.com \
--to=joerg.roedel-5c7gfcevmho@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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