Re: [edk2] [Xen-devel] [PATCH RFC 02/18] OvmfPkg: Add basic skeleton for the Xenbus driver.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 01:25:03PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:31PM +0100, Anthony PERARD wrote: > > This includes Component Name and Driver Binding. > > The title says driver, but the cover letter said 'bus driver'. > Should it have bus driver in it? Do yo

Re: [edk2] [Xen-devel] [PATCH RFC 03/18] OvmfPkg/XenbusDxe: Add device state struct and create an ExitBoot services event.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 01:32:54PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:32PM +0100, Anthony PERARD wrote: > > The ExitBoot event is used to disconnect from the device before the > > next operating system start using them. > > > > Contributed-under: TianoCore Contribu

Re: [edk2] [Xen-devel] [PATCH RFC 05/18] OvmfPkg/XenbusDxe: Open PciIo protocol.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 01:39:36PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:34PM +0100, Anthony PERARD wrote: > > Contributed-under: TianoCore Contribution Agreement 1.0 > > Signed-off-by: Anthony PERARD > > Could you describe a bit why you need to use it? > > I think

Re: [edk2] [Xen-devel] [PATCH RFC 06/18] OvmfPkg: Introduce Xenbus Protocol.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 01:42:09PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:35PM +0100, Anthony PERARD wrote: > > This protocol will be used for communication between a PV driver (like a > > PV block driver) and the Xenbus/Xenstore. > > > > Contributed-under: TianoCore C

Re: [edk2] [Xen-devel] [PATCH RFC 08/18] OvmfPkg/XenbusDxe: Add Grant Table functions.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 01:48:22PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:37PM +0100, Anthony PERARD wrote: > > There are used to grant access of pages to other Xen domains. > > > > This code originaly comes from the Xen Project, and more precisely from > > MiniOS. >

Re: [edk2] [Xen-devel] [PATCH RFC 14/18] OvmfPkg/XenbusDxe: Indroduce XenBus support itself.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 03:04:50PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:43PM +0100, Anthony PERARD wrote: > > This is a bus-like on top of Xenstore. It will look for advertised > > ParaVirtualized devices and initialize them by producing XenBus > > protocol. > > > >

Re: [edk2] Enc.: [PATCH] - ShellPkg: Some improvements in space handling, "if" command and user input reading

2014-07-18 Thread Leandro Becker
Hello, Following instructions from Jaben. Please guys, check this patch. === ShellPkg: Improvements in space handling Improvements in space handling at command lines to accept tab (\t) as a space. Contributed-under: TianoCore Contribution Ag

Re: [edk2] [Xen-devel] [PATCH RFC 17/18] OvmfPkg/XenPvBlkDxe: Add BlockFront client.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 03:41:17PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:46PM +0100, Anthony PERARD wrote: > > This is the code that will do the actual communication between OVMF and > > a PV block backend, where the block device lives. > > > > This implementation ori

Re: [edk2] [Xen-devel] [PATCH RFC 00/18] Introducing Xen PV block driver to OVMF

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 04:10:49PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:29PM +0100, Anthony PERARD wrote: > > Hi all, > > > > This patch series is implementing the necessary in order to access a PV > > block > > device. For that, one need a XenStore client, a XenBus

Re: [edk2] [Xen-devel] [PATCH RFC 18/18] OvmfPkg/XenPvBlkDxe: Add BlockIo.

2014-07-18 Thread Anthony PERARD
On Wed, Jul 16, 2014 at 03:57:23PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 16, 2014 at 04:15:47PM +0100, Anthony PERARD wrote: > > Install the BlockIo protocol. > > > > Contributed-under: TianoCore Contribution Agreement 1.0 > > Signed-off-by: Anthony PERARD > > --- > > OvmfPkg/XenPvBl

Re: [edk2] rhel UEFI OS hang due to memory map missmatch after ExitBootService()

2014-07-18 Thread Kinney, Michael D
Ritul, UEFI Specification does cover this scenario in the detailed description of ExitBootServices() in Section 6.4: An EFI OS loader must ensure that it has the system's current memory map at the time it calls ExitBootServices(). This is done by passing in the current memory map's MapKey valu

[edk2] Error building OvmfPkg

2014-07-18 Thread Mendyke, DanielX
I'm running Archlinux kernel 3.15 Using gcc 4.9 Python 2.7.8 I downloaded a current snapshot of OvmfPkg. When running the 'build.sh' command I receive the following error message: GenFw: Error 3000: Invalid Unsupported section alignment Also "err

Re: [edk2] Error building OvmfPkg

2014-07-18 Thread Andrew Fish
On Jul 18, 2014, at 3:21 PM, Mendyke, DanielX wrote: > > I’m running Archlinux kernel 3.15 > Using gcc 4.9 > Python 2.7.8 > > I downloaded a current snapshot of OvmfPkg. > When running the ‘build.sh’ command I receive the following error message: > > GenFw: Error 3000: Inva

Re: [edk2] Error building OvmfPkg

2014-07-18 Thread Jordan Justen
On Fri, Jul 18, 2014 at 3:21 PM, Mendyke, DanielX wrote: > When running the ‘build.sh’ command I receive the following error message: > GenFw: Error 3000: Invalid > Unsupported section alignment Someone reported this issue a few weeks back on irc. I

Re: [edk2] Error building OvmfPkg

2014-07-18 Thread Andrew Fish
On Jul 18, 2014, at 4:42 PM, Jordan Justen wrote: > On Fri, Jul 18, 2014 at 3:21 PM, Mendyke, DanielX > wrote: >> When running the ‘build.sh’ command I receive the following error message: >>GenFw: Error 3000: Invalid >>Unsupported section alignme

[edk2] [PATCH v2 0/2] OvmfPkg: split the variable store to a separate file

2014-07-18 Thread Laszlo Ersek
Version 2 of my similar patch, originally posted in last November. Rather than introducing a new build option (-D SPLIT_VARSTORE in v1), we now build three files, a full image (as before) and the two split files in addition. This complicates the patchset somewhat, because simply repeating / updati

[edk2] [PATCH v2 1/2] OvmfPkg: extract varstore-related FD Layout Regions to an include file

2014-07-18 Thread Laszlo Ersek
This saves code duplication between the Ia32, Ia32X64, and X64 flavors, and enables the next patch to include the varstore in new FD files by reference. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek --- OvmfPkg/OvmfPkgIa32.fdf| 67 +--

[edk2] [PATCH v2 2/2] OvmfPkg: build OVMF_VARS.fd, OVMF_CODE.fd, OVMF.fd

2014-07-18 Thread Laszlo Ersek
OVMF_VARS.fd and OVMF_CODE.fd split the variable store and the firmware code in separate files. The PCDs' values continue to depend only on FD_SIZE_1MB vs. FD_SIZE_2MB. With the split files, it must be ensured on the QEMU command line that OVMF_VARS.fd and OVMF_CODE.fd be contiguously mapped so th