From: Stijn De Weirdt <stijn.deweirdt@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
"Ronald G. Minnich" <rminnich@lanl.gov>,
xen-devel@lists.sourceforge.net
Subject: Re: 'Sloppier' PCI access checks in main tree
Date: Wed, 12 Jan 2005 09:27:58 +0100 [thread overview]
Message-ID: <aa7056bb05011200275e02eddc@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12328D@liverpoolst.ad.cl.cam.ac.uk>
sorry missed this email.
i'm using 2.4.28. i'll try today, since i have to recompile my kernel
anyway. reaction times on my system are anything but good (what
performace loss should i expect if i use a file-backed vbd (and what
fs is the most for those). also network seems pretty slow.
stijn
On Sat, 8 Jan 2005 18:42:16 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> Stijn,
>
> What kernel are you using? We've all been working on the assumption that
> you were using 2.6, but the problem your seeing would be consistent with
> using 2.4, which only has support for basic X servers. If you are using
> 2.4 try disabling the int10/bios/vesa X drivers etc.
>
> [Our /dev/mem under 2.4 doesn't support read/write only mmap.]
>
> Ian
>
> > -----Original Message-----
> > From: xen-devel-admin@lists.sourceforge.net
> > [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of
> > Keir Fraser
> > Sent: 08 January 2005 17:22
> > To: Ronald G. Minnich
> > Cc: Stijn De Weirdt; xen-devel@lists.sourceforge.net
> > Subject: [Xen-devel] 'Sloppier' PCI access checks in main tree
> >
> > > As I read this, the module loader tried to run the vga bios
> > and failed, as
> > > it could not get to the actual BIOS code? That's how it looks to me
> > > anyway.
> > >
> > > I have no idea: has anyone seen option rom access working
> > under Xen? I
> > > have not, but I have not tried this recently. The VGA bios
> > ROM is not
> > > accessible on my laptop, however.
> > >
> > > Does Xen currently allow a guest to set enable the option
> > rom access and
> > > set the register (0x30 I think) for the option ram base address?
> >
> > I've just checked in sloppoer PCI checking for 2.0-testing and
> > unstable trees. It should help for those drivers that need to monkey
> > with the base-address config registers (we had previously been
> > disallowing that). Really, applying any check finer-grained than
> > "should this domain be allowed to access this device?" is hard as
> > various drivers need to do all kinds of weird things with the
> > config-register space.
> >
> > Hopefully this may help you get further in getting AGP to work on your
> > system!
> >
> > -- Keir
> >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-12 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 18:42 'Sloppier' PCI access checks in main tree Ian Pratt
2005-01-12 8:27 ` Stijn De Weirdt [this message]
2005-01-12 8:39 ` Ian Pratt
2005-01-12 16:48 ` Stijn De Weirdt
2005-01-12 18:18 ` Ian Pratt
2005-01-13 15:10 ` Stijn De Weirdt
-- strict thread matches above, loose matches on Subject: below --
2005-01-08 17:22 Keir Fraser
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=aa7056bb05011200275e02eddc@mail.gmail.com \
--to=stijn.deweirdt@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rminnich@lanl.gov \
--cc=xen-devel@lists.sourceforge.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.