From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ABI change proposal before the 2.6.22 freeze
Date: Sun, 13 May 2007 15:17:01 +0300 [thread overview]
Message-ID: <464701BD.7050707@qumranet.com> (raw)
In-Reply-To: <4643518D.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Gregory Haskins wrote:
> (assuming that hasn't happened already?)
>
> One thing that would make my life easier going forward would be if we could separate out the interrupt related state from the [gs]et_sregs() calls. What I propose is that we make two new calls (say [gs]et_pic). For "level-0" mode this will be saving/restoring the 256-bit "userint" array. For other modes, it will be saving whatever is relevant for the APIC (registers, etc). The userspace code would be aware of which mode it is operating under anyway, since it has to enable the feature.
>
While we can slip in such a change to mainline, we're committed to
supporting the current ABI for Fedora 7, so there's not much point.
However, I don't see an issue. You could specify that when the feature
is enabled, the irq state in get/set sregs is ignored, and the new
functions are to be used.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-05-13 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 21:09 ABI change proposal before the 2.6.22 freeze Gregory Haskins
[not found] ` <4643518D.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-05-13 8:17 ` Dor Laor
2007-05-13 12:17 ` 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=464701BD.7050707@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@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