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

* Keir Fraser (Keir.Fraser@cl.cam.ac.uk) wrote:
> 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.

OK, that's more or less what I was thinkg (re: no-ops).

> 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. 

My intention was more about being able to run more code paths without
having #if CONFIG_XEN if possible to hand to trivial or no-op stub
instead.

  reply	other threads:[~2005-08-22 18:57 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
2005-08-22 18:57       ` Chris Wright [this message]
  -- 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=20050822185755.GY7762@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=aravindh.puthiyaparambil@unisys.com \
    --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.