[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] KEXEC: fix kexec_get_range_compat to fail vocally
On 05/12/11 12:58, Jan Beulich wrote: >>>> On 05.12.11 at 12:35, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote: >> I am not sure that this is the only instance, but it is really not >> acceptable to hand truncated pointers or sizes for physical memory to dom0. > While I agree to the change, I think we also ought to add a new flavor > of KEXEC_CMD_kexec_get_range that is 64-bit capable even for a > 32-bit Dom0. Agreed - I am working on introducing a new hypercall right now. > Both under the assumption that apart from the truncation nothing > prevents addresses above the 4G boundary from being usable with > a 32-bit kernel for at least one of the ranges (probably only > KEXEC_RANGE_MA_CPU and KEXEC_RANGE_MA_VMCOREINFO are > candidates for this on x86). Will those ranges not be covered by my patch? > Jan > -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |