From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Handling PCI/ROM space
Date: Wed, 18 Oct 2006 15:14:12 -0700 [thread overview]
Message-ID: <4536A734.7030904@vmware.com> (raw)
In-Reply-To: <45369FD4.3030303@goop.org>
Jeremy Fitzhardinge wrote:
> I'm seeing oopses in probe_roms() and pci_find_bios(), apparently
> because those pages are not mapped under Xen. I'm not sure why I'm
> seeing this now and not before, but I suspect its because I enabled
> CONFIG_DEBUG_PAGEALLOC. Anyway, I've got these patches to deal with
> these cases:
Probably a config file difference - GOBIOS vs GODIRECT.
These patches look fine, although is there a more general solution?
Like bypassing the whole PCI ROM probing entirely? We don't really want
to use the PCI ROM here either, although we have a slightly worse
problem - the pages are mapped and do have a PCI ROM. Perhaps
paravirt-ops should be able to flip a global switch to disable this
(perhaps already there?).
Zach
next prev parent reply other threads:[~2006-10-18 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 21:42 Handling PCI/ROM space Jeremy Fitzhardinge
2006-10-18 22:14 ` Zachary Amsden [this message]
2006-10-18 22:24 ` Jeremy Fitzhardinge
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=4536A734.7030904@vmware.com \
--to=zach@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).