From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christophe Saout <christophe@saout.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen with dom0 pvops on ultra-recent "git tip" kernel on x86_64
Date: Fri, 16 Jan 2009 09:23:51 -0800 [thread overview]
Message-ID: <4970C2A7.8010702@goop.org> (raw)
In-Reply-To: <1231865847.5257.8.camel@leto.intern.saout.de>
Christophe Saout wrote:
> Hello,
>
>
>> The X server crashes in some I/O port "inb()" command. Seems like the
>> io permissions aren't correctly passed through or something. (iopl or
>> ioperm or so) I'll try to debug a bit more later.
>>
>
> The native Xen kernel has an arch/x86/kernel/ioport-xen.c which calls:
>
> HYPERVISOR_physdev_op(PHYSDEVOP_set_iobitmap, &set_iobitmap);
>
> Is this a feature mabye still missing from the paravirtualized Xen?
>
> If yes, what would it take? A new paravirt call?
>
Hi Christophe,
Firstly, thanks a lot for trying out the pvops dom0 and doing so much
debugging on it. I'm still catching up on my rather daunting email
backlog - including your torrent of messages - so feel free to remind me
about/resent anything important which still needs looking at.
I haven't been brave enough to even attempt starting X; there's a lot of
work to be done if you want to do anything beyond dumb framebuffer.
Anyway, in this case, I definitely haven't added this call, so it will
need to be done somewhere. Does it need to be called once at startup,
or on every context switch? There may well be a suitable place to hook
this into already, but we can add a new pvop if its really needed.
J
next prev parent reply other threads:[~2009-01-16 17:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 19:22 Xen with dom0 pvops on ultra-recent "git tip" kernel on x86_64 Christophe Saout
2009-01-10 20:11 ` Marc - A. Dahlhaus
2009-01-10 20:28 ` Christophe Saout
2009-01-10 20:37 ` Pasi Kärkkäinen
2009-01-10 20:49 ` Marc - A. Dahlhaus
2009-01-10 20:54 ` Christophe Saout
2009-01-10 21:13 ` Christophe Saout
2009-01-11 14:17 ` Christophe Saout
2009-01-11 14:52 ` Christophe Saout
2009-01-11 16:35 ` Christophe Saout
2009-01-11 16:59 ` Christophe Saout
2009-01-11 20:13 ` Christophe Saout
2009-01-12 14:17 ` Christophe Saout
2009-01-12 16:41 ` Christophe Saout
2009-01-13 9:28 ` Christophe Saout
2009-01-13 15:33 ` Pasi Kärkkäinen
2009-01-13 16:41 ` Christophe Saout
2009-01-13 16:57 ` Christophe Saout
2009-01-16 17:23 ` Jeremy Fitzhardinge [this message]
2009-01-16 17:40 ` Christophe Saout
2009-01-16 17:52 ` Jeremy Fitzhardinge
2009-01-17 16:29 ` Christophe Saout
2009-01-18 20:10 ` Christophe Saout
2009-01-18 21:28 ` Christophe Saout
2009-01-18 22:39 ` Xen with dom0 pvops on ultra-recent "git tip"kernel " Keir Fraser
2009-01-19 9:52 ` Christophe Saout
2009-01-19 12:33 ` Christophe Saout
2009-02-22 23:28 ` Jeremy Fitzhardinge
2009-02-24 9:32 ` Christophe Saout
2009-02-24 10:41 ` Christophe Saout
2009-02-24 16:20 ` Boris Derzhavets
2009-02-24 21:22 ` Jeremy Fitzhardinge
2009-02-24 21:51 ` Andrew Lyon
2009-02-25 7:16 ` Boris Derzhavets
2009-04-23 21:49 ` Nvidia drivers on " Nigel Gamble
2009-04-24 7:43 ` Andrew Lyon
[not found] ` <1240816930.4387.18.camel@petrie>
2009-04-28 0:07 ` Jeremy Fitzhardinge
2009-04-28 5:33 ` William Pitcock
2009-04-29 15:13 ` Attempt to load the most recent 2.6.30-rc-tip under Xen-3.3.1 on F11-preview Boris Derzhavets
2009-04-29 15:58 ` Boris Derzhavets
2009-04-29 16:35 ` Jeremy Fitzhardinge
2009-04-29 18:42 ` Boris Derzhavets
2009-02-25 6:39 ` Xen with dom0 pvops on ultra-recent "git tip"kernel on x86_64 Boris Derzhavets
2009-01-20 20:08 ` Xen with dom0 pvops on ultra-recent "git tip" kernel " Jeremy Fitzhardinge
2009-01-20 21:27 ` Pasi Kärkkäinen
2009-01-21 18:32 ` Andrew Lyon
2009-01-26 19:56 ` Adam Wendt
2009-01-13 18:16 ` Pasi Kärkkäinen
2009-01-16 17:26 ` Jeremy Fitzhardinge
2009-01-16 18:22 ` Pasi Kärkkäinen
2009-01-10 20:40 ` Marc - A. Dahlhaus
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=4970C2A7.8010702@goop.org \
--to=jeremy@goop.org \
--cc=christophe@saout.de \
--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.