From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: access shared_info?
Date: Wed, 07 Jun 2006 18:27:29 +0200 [thread overview]
Message-ID: <4486FE71.9090606@suse.de> (raw)
In-Reply-To: <7c8cd23f1fb1eafe50db8bf82cadad3a@cl.cam.ac.uk>
>> How about the attached patch? It makes /proc/iomem under xen dom0 look
>> like on native hardware. Also for domU it has some sensible values then
>> instead of being empty.
>
> Plausible, perhaps with cleanup (e.g., why change the prototype of
> legacy_init_iomem_resource
Well, there is no point in carring around those two arguments. It's not
needed, and the third one (crash kernel area) isn't passed though
anyway. So while touching it anyway I've dropped them as cleanup. Not
exactly xen-related, I can try to push that upstream too ;)
> and remove non-Xen code, increasing the diff
> against native?).
Where is non-xen code removed?
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-06-07 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 13:28 access shared_info? Gerd Hoffmann
2006-06-07 13:48 ` Keir Fraser
2006-06-07 15:53 ` Gerd Hoffmann
2006-06-07 16:04 ` Keir Fraser
2006-06-07 16:27 ` Gerd Hoffmann [this message]
2006-06-07 16:47 ` Keir Fraser
2006-06-07 16:59 ` Gerd Hoffmann
2006-06-07 17:27 ` Gerd Hoffmann
2006-06-07 21:55 ` Chris Wright
2006-06-08 7:32 ` Keir Fraser
2006-06-09 13:44 ` Gerd Hoffmann
2006-06-09 13:59 ` Ian Campbell
2006-06-09 14:16 ` Gerd Hoffmann
2006-06-09 14:35 ` Keir Fraser
2006-06-09 17:34 ` Chris Wright
2006-06-09 17:23 ` Chris Wright
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=4486FE71.9090606@suse.de \
--to=kraxel@suse.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.