From: ebiederm@xmission.com (Eric W. Biederman)
To: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Cc: "Grant Grundler" <iod00d@hp.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
fastboot@osdl.org, linux-ia64@vger.kernel.org,
Jesse Barnes <jbarnes@engr.sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: [BROKEN PATCH] kexec for ia64
Date: 05 Aug 2004 15:29:09 -0600 [thread overview]
Message-ID: <m18yct2s0q.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB00750E615@fmsmsx406.amr.corp.intel.com>
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com> writes:
> >On Wed, Aug 04, 2004 at 08:14:55PM -0600, Eric W. Biederman wrote:
> >> VGA/serial console devices rarely need to do be bus masters so they
> >> should be fine.
> >
> >yeah - you are right. I wasn't thinking.
> >Can anyone comment on UGA or other console devices?
>
> UGA is essentially a PCI device. It uses the EFI PCI I/O
> protocol which gets glued to the kernels pci layer...at least in
> a prototype.
>
> I haven't looked at the latest kexec patch. How is it handling
> the call to EFI's SetVirtualAddressMap()? Is it part of the config
> associated with kexec to do efi calls in physical mode only so that
> it doesn't have to contend with potential follow-on invocations
> resultant from "the next" kernel's initialization?
It should be. So far all I have seen are tentative ia64 kexec patches.
Eric
next prev parent reply other threads:[~2004-08-05 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:44 Tolentino, Matthew E
2004-08-05 21:29 ` Eric W. Biederman [this message]
[not found] <200407261524.40804.jbarnes@engr.sgi.com>
[not found] ` <200407261536.05133.jbarnes@engr.sgi.com>
[not found] ` <20040730155504.2a51b1fa.rddunlap@osdl.org>
2004-08-04 13:07 ` Eric W. Biederman
2004-08-04 23:33 ` Grant Grundler
2004-08-05 2:14 ` [Fastboot] " Eric W. Biederman
2004-08-05 15:39 ` Grant Grundler
2004-08-05 16:44 ` Eric W. Biederman
2004-08-05 16:45 ` Luck, Tony
2004-08-05 17:05 ` [Fastboot] " Eric W. Biederman
2004-08-05 19:18 ` Khalid Aziz
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=m18yct2s0q.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=iod00d@hp.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=rddunlap@osdl.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
Powered by JetHome