[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1fy5b1pui.fsf@ebiederm.dsl.xmission.com>
Date: Fri, 01 Jun 2007 12:39:33 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Chandramouli Narayanan <mouli@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, ak@...e.de,
akpm@...ux-foundation.org, Randy Dunlap <randy.dunlap@...cle.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Jeremy Fitzhardinge" <jeremy@...p.org>,
"Yinghai Lu" <yhlu.kernel@...il.com>
Subject: Re: [PATCH 2.6.21 1/3] x86_64: EFI64 support
Sorry for the late replay I missed this patch series going by the first time.
> +static efi_status_t
> +phys_efi_set_virtual_address_map(unsigned long memory_map_size,
> + unsigned long descriptor_size,
> + u32 descriptor_version,
> + efi_memory_desc_t *virtual_map)
> +{
> + efi_status_t status;
> +
> + efi_call_phys_prelog();
> + status = efi_call_phys(efi_phys.set_virtual_address_map,
> + EFI_ARG_NUM_SET_VIRTUAL_ADDRESS_MAP,
> + (unsigned long)memory_map_size,
> + (unsigned long)descriptor_size,
> + (unsigned long)descriptor_version,
> + (unsigned long)virtual_map);
> + efi_call_phys_epilog();
> + return status;
> +}
Please, Please kill this.
As far as I can tell virtual mode is incompatible with kexec.
It is unnecessary because none of the EFI calls are fast path.
Further I believe that using virtual addresses is likely to
make things more brittle.
So please drop the EFI virtual mode nonsense.
Thank you,
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists