From: "Gregory Haskins" <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: ABI change proposal before the 2.6.22 freeze
Date: Thu, 10 May 2007 17:09:04 -0400 [thread overview]
Message-ID: <4643518D.BA47.005A.0@novell.com> (raw)
(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.
The benefit here is that this is a simple change that we can slip in now before the ABI is frozen. IIUC, we have already been changing the ABI in the trunk recently anyway. I am just thinking that the LAPIC work I am doing probably wont make it in before the freeze, but this small change surely could.
Thoughts? I can put together a patch if there is acceptance of the idea.
-Greg
-------------------------------------------------------------------------
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/
next reply other threads:[~2007-05-10 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 21:09 Gregory Haskins [this message]
[not found] ` <4643518D.BA47.005A.0-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
2007-05-13 8:17 ` ABI change proposal before the 2.6.22 freeze Dor Laor
2007-05-13 12:17 ` 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=4643518D.BA47.005A.0@novell.com \
--to=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