From: ebiederm@xmission.com (Eric W. Biederman)
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Suparna Bhattacharya <suparna@in.ibm.com>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
fastboot@osdl.org, Werner Almesberger <wa@almesberger.net>
Subject: Re: kexec for 2.5.44 (Who do I send this to?)
Date: 30 Oct 2002 08:53:33 -0700 [thread overview]
Message-ID: <m1vg3jhqiq.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20021030140238.GE12540@atrey.karlin.mff.cuni.cz>
Pavel Machek <pavel@suse.cz> writes:
> Hi!
>
> > [snip] discussion on how to model IOAPIC and pic and cpus using
> > the device model.
> >
> > I now need to go code this thing don't I? Or did I get lucky
> > and get you interested Pavel?
>
> I'm not sure if putting APICS above PCI will look right to
> Patrick... You'd better ask him. (Sorry, I was offline for > week.)
Ok I will. I primarily meant to put an APIC bus above pci. And maybe
filter the APICS down. The real challenge is that the APIC connection is
in parallel with the PCI connection. It would take a DAG to truly model
the connections between hardware, and I have been told that people don't want that...
Eric
next prev parent reply other threads:[~2002-10-30 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 10:10 kexec for 2.5.44 (Who do I send this to?) Eric W. Biederman
2002-10-19 19:23 ` Bill Davidsen
2002-10-19 21:36 ` Eric W. Biederman
2002-10-20 23:02 ` Rob Landley
2002-10-21 12:31 ` Alan Cox
2002-10-21 14:51 ` Eric W. Biederman
2002-10-21 20:54 ` Bill Davidsen
2002-10-20 19:09 ` Pavel Machek
2002-10-26 13:54 ` Eric W. Biederman
2002-10-27 17:44 ` Eric W. Biederman
2002-10-27 22:51 ` Eric W. Biederman
2002-10-30 14:02 ` Pavel Machek
2002-10-30 15:53 ` Eric W. Biederman [this message]
2002-10-28 8:16 ` [CFT] [PATCH] kexec 2.5.44 (minimal) Eric W. Biederman
2002-10-30 22:41 ` Andy Pfiffer
2002-10-31 3:59 ` Eric W. Biederman
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=m1vg3jhqiq.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=suparna@in.ibm.com \
--cc=wa@almesberger.net \
/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.