From: Manuel Bernhardt <mailinglist@prodigy7.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problem access hardware with xen 3.0 unstable
Date: Sat, 08 Oct 2005 12:49:27 +0200 [thread overview]
Message-ID: <4347A437.3020600@prodigy7.de> (raw)
In-Reply-To: <6d32c7c140ca5de53b58065cd01c4d48@cl.cam.ac.uk>
It's ok so - i think stabilisation and domU interface freezes for
production use in the industrie is a "little bit" more important like my
problems which appears during "home use" of xen :-)
manuel
Keir Fraser schrieb:
>
> I'm afraid so. We currently have no interface for unprivileged domains
> to access PCI space. If we gave a domU unfettered access to PCI space
> and BIOS tables there would be a big conflict betwene that domain and
> domain0.
>
> This isn't going to be very hard to fix, but stabilisation and domU
> interface freezes come first.
>
> -- Keir
>
prev parent reply other threads:[~2005-10-08 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 21:08 Problem access hardware with xen 3.0 unstable Manuel Bernhardt
2005-10-07 22:03 ` Keir Fraser
2005-10-08 10:14 ` Manuel Bernhardt
2005-10-08 10:49 ` Keir Fraser
2005-10-08 10:49 ` Manuel Bernhardt [this message]
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=4347A437.3020600@prodigy7.de \
--to=mailinglist@prodigy7.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.