From: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Carsten Otte <carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
"Zhang,
Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: architecture-specific data in struct kvm_run ?
Date: Thu, 10 Jan 2008 09:30:04 +0100 [thread overview]
Message-ID: <4785D78C.7060405@de.ibm.com> (raw)
In-Reply-To: <1199920800.5637.58.camel@basalt>
Hollis Blanchard wrote:
> There are a bunch of x86-specific fields in struct kvm_run:
> /* in */
> __u8 request_interrupt_window;
> __u8 padding1[7];
>
> /* out */
> __u8 if_flag;
> __u8 padding2[2];
>
> /* in (pre_kvm_run), out (post_kvm_run) */
> __u64 cr8;
> __u64 apic_base;
>
> Since this structure is shared with all architectures, can we find a
> more appropriate place to keep this data? Or should we feel free to add
> arch-specific data here?
Afaics, we'll need an arch extension to kvm_run. On s390, we'll need
different extensions then x86 has defined here. And we don't need any
of above fields.
Carsten
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
prev parent reply other threads:[~2008-01-10 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 23:20 architecture-specific data in struct kvm_run ? Hollis Blanchard
2008-01-10 1:36 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCC08A9F-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-10 9:47 ` Avi Kivity
2008-01-10 8:30 ` Carsten Otte [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=4785D78C.7060405@de.ibm.com \
--to=cotte-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
--cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@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