All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ron Arts <ron.arts@netland.nl>
To: maw48@cantab.net
Cc: xen-devel@lists.sourceforge.net
Subject: Re: isa_bus_to_virt_needs_PRIVILEGED_BUILD
Date: Fri, 31 Dec 2004 10:27:51 +0100	[thread overview]
Message-ID: <41D51B97.7070401@netland.nl> (raw)
In-Reply-To: <Prayer.1.0.11.0412301433290.7724@hermes-1.csi.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

Okay,

So far I thought the xen0 kernel was only to be used for the
first domain (which is called domain 0 in the documentation,
hence my confusion).

After reading the docs more thoroughly, I discovered the
concept of 'driver domains' which can be used as 'backends
for other domains'.

So, apparently you can use xen0 kernels more than
once on a machine, and you can use them to support
hardware.

But what is a backend domain, and how does it connect
to a driver domain?

Is that described somewhere?

Ron


M.A. Williamson wrote:
>> Does anyone know how I can detect if some hardware is actually assigned
>> to some domain (apart from loading the device driver)? lspci
>> does not work (/proc/bus/pci not present).
> 
> 
> lspci should Just Work(TM). Are you using a xen0 kernel in that domain? 
> The xenU kernel doesn't have any PCI support.
> 
> Cheers,
> Mark
> 
>> Ron
>>
>> PS: The doc error:
>>   pci_dom0_hide=(xx.xx.x)(yy.yy.y)... should be
>>   physdev_dom0_hide=(xx:xx.x)(yy:yy.y)...
>>
>>
>> Keir Fraser wrote:
>> >>Hi,
>> >>
>> >>What does this mean? Having read the FAQ I can guess what
>> >>it means, but will this be solved eventually?
>> > > > What version of Xen is this? Looking at ioremap.c I don't see 
>> how your
>> > build can fail -- __ioremap() is conditional on
>> > CONFIG_XEN_PHYSDEV_ACCESS, as is the definition of isa_bus_to_virt in
>> > asm-xen/asm-i386/io.h. i.e., if isa_bus_to_virt is not defined, then
>> > neither is __ioremap.
>> > >  -- Keir
>> >
>>
> 

-- 
Netland Internet Services
bedrijfsmatige internetoplossingen

http://www.netland.nl   Kruislaan 419              1098 VA Amsterdam
info: 020-5628282       servicedesk: 020-5628280   fax: 020-5628281

Op dit bericht is de volgende disclaimer van toepassing:
http://www.netland.nl/maildisclaimer

RENTAL CAR: The only *TRUE* all-terrain vehicle.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3228 bytes --]

  reply	other threads:[~2004-12-31  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30  8:38 isa_bus_to_virt_needs_PRIVILEGED_BUILD Ron Arts
2004-12-30  9:15 ` isa_bus_to_virt_needs_PRIVILEGED_BUILD Keir Fraser
2004-12-30 11:44   ` isa_bus_to_virt_needs_PRIVILEGED_BUILD Ron Arts
2004-12-30 14:33     ` isa_bus_to_virt_needs_PRIVILEGED_BUILD M.A. Williamson
2004-12-31  9:27       ` Ron Arts [this message]
2004-12-31 15:34         ` isa_bus_to_virt_needs_PRIVILEGED_BUILD M.A. Williamson

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=41D51B97.7070401@netland.nl \
    --to=ron.arts@netland.nl \
    --cc=maw48@cantab.net \
    --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.