From: Jeremy Katz <katzj-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org,
Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
"Zhang,
Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: How to handle kvm-abi-10 case for other archs.
Date: Mon, 03 Dec 2007 08:09:11 -0500 [thread overview]
Message-ID: <1196687351.3300.18.camel@localhost.localdomain> (raw)
In-Reply-To: <47513308.9020407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
> Zhang, Xiantao wrote:
> > I think new archs for kvm doesn't need to care about kvm-abi
> > case in their code, since current abi is bigger than 10. But in current
> > libkvm.c, we can see that many abi-specific code in it. How to handle it
> > ? Can we use __x86__ macro to make it sightless for other archs or
> > other good methods ?
> >
>
> #ifdef is okay for this. Actually we can probably remove abi 10 support
> since the F7 kernel now supports the modern ABI (I don't think anybody
> else uses abi 10, which is pre 2.6.22 when we announced ABI compatibility.
>
> Jeremy, is removing abi 10 support fine with you? I note that both the
> kernel supports the new ABI and F7 userspace doesn't require it, so
> we're fine on both counts.
Yeah, that sounds like it should be fine. The updates have been out for
quite a while at this point
Jeremy
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
next prev parent reply other threads:[~2007-12-03 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 4:00 How to handle kvm-abi-10 case for other archs Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCA39867-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-01 10:10 ` Avi Kivity
[not found] ` <47513308.9020407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-03 13:09 ` Jeremy Katz [this message]
[not found] ` <1196687351.3300.18.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-12-03 13:30 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCA39CD4-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-04 18:24 ` Avi Kivity
[not found] ` <47559B48.90702-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-05 0:04 ` Zhang, Xiantao
2007-12-04 18:49 ` Carlo Marcelo Arenas Belon
2007-12-05 14:16 ` 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=1196687351.3300.18.camel@localhost.localdomain \
--to=katzj-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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