All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Chris Wright <chrisw@osdl.org>
Cc: xen-devel@lists.xensource.com, "Puthiyaparambil,
	Aravindh" <aravindh.puthiyaparambil@unisys.com>
Subject: Re: [RFC] Genapic in x86_64 Dom0
Date: Mon, 22 Aug 2005 19:48:24 +0100	[thread overview]
Message-ID: <E1E7HLM-0002Li-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Mon, 22 Aug 2005 11:20:36 PDT." <20050822182036.GV7762@shell0.pdx.osdl.net>

> * Keir Fraser (Keir.Fraser@cl.cam.ac.uk) wrote:
> > Perhaps genapic_xen is currently being too smart for its own good? :-)
> 
> Hehe, quite possible ;-)
> 
> > On i386 we lobotomised local apic handling.
> 
> My goal was to avoid (equivalent of) #if 0 where possible, by backfilling
> functionality where possible.  I also had filled out mpc_config_processor
> during mp_register_lapic and tried to maintain the physid map (that bit
> isn't merged).  Do you think there's value in maintaining that level of
> code compatibility?

I suspect we might be best off just diverging completely and having
our own file that implements enough of the local APIC "interface" to
get everything else to build, but is basically a set of no-ops. That's
basically what we have for arch/xen/i386.

Maintaining processor and lapic info is pretty pointless since those
things aren't under domain 0's control, although it may be as easy to
do so as not. 

 -- Keir

  reply	other threads:[~2005-08-22 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 20:25 [RFC] Genapic in x86_64 Dom0 Puthiyaparambil, Aravindh
2005-08-20  9:45 ` Keir Fraser
2005-08-22 18:20   ` Chris Wright
2005-08-22 18:48     ` Keir Fraser [this message]
2005-08-22 18:57       ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2005-08-22 16:14 Puthiyaparambil, Aravindh

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=E1E7HLM-0002Li-00@mta1.cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=aravindh.puthiyaparambil@unisys.com \
    --cc=chrisw@osdl.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.