From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gregory Haskins" Subject: ABI change proposal before the 2.6.22 freeze Date: Thu, 10 May 2007 17:09:04 -0400 Message-ID: <4643518D.BA47.005A.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org (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/