|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] access shared_info?
>> 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@xxxxxxx>
http://www.suse.de/~kraxel/julika-dora.jpeg
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Keir Fraser
- Re: [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Keir Fraser
- Re: [Xen-devel] access shared_info?,
Gerd Hoffmann <=
- Re: [Xen-devel] access shared_info?, Keir Fraser
- Re: [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Chris Wright
- Re: [Xen-devel] access shared_info?, Keir Fraser
- Re: [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Ian Campbell
- Re: [Xen-devel] access shared_info?, Gerd Hoffmann
- Re: [Xen-devel] access shared_info?, Keir Fraser
- Re: [Xen-devel] access shared_info?, Chris Wright
|
|
|
|
|