[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] access shared_info?

On 7 Jun 2006, at 17:27, Gerd Hoffmann wrote:

Plausible, perhaps with cleanup (e.g., why change the prototype of

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?

Oh, I see it's moved to a new function. I guess that's okay, although couldn't you fake up an e820 map and call legacy_init_iomem_resource on the domU path, rather than having to pull code out into a new function? Does this patch change behaviour for dom0 at all? I think /proc/iomem already looks like native there? Also the patch will need to include x86/64 too.

  -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.