similar to: [RFC v1 0/3] Add VIRTIO_F_IOMMU_PLATFORM support

E820 definitions copied from IntelFrameworkModulePkg/Csm/ LegacyBiosDxe/LegacyBiosInterface.h. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> --- OvmfPkg/Include/IndustryStandard/E820.h | 46 +++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode

On Sat, Jun 8, 2013 at 7:39 PM, Laszlo Ersek <lersek at redhat.com> wrote: > Patches before the last are small cleanups. > > In the last patch I'm trying to extract / generalize an idea from Stefan > Hajnoczi's review of my virtio-net driver for OVMF. > > Unfortunately I can't find Stefan's email on any mailing list archive > (sourceforge, gmane,

Regarding patches 5-7, it seems like the mem-map code flow could be more shared. It is a bit challenging to unravel things though. I guess the only specific thing I can really point out is that PcdPciAllowFullEnumeration should be initialized in a different patch, and not within the mem-map init path. -Jordan On Tue, Nov 19, 2013 at 12:38 PM, Wei Liu <wei.liu2@citrix.com> wrote: > This

Hi all Manage to pull together another prototype without any hack in it. The first patch adds PcdPciAllowFullEnumeration in MdeModulePkg, which short-cuts full enumeration if set to false. This one should be helpful to QEMU as well. This patch set should work with QEMU / KVM as well (read: doesn''t break). The code path is the same as before if Xen is not detected. Comments are

EFI_XEN_OVMF_INFO is defined to accept configurations from hvmloader. It must match the definition on Xen side. XenInfo is extended to include necessary bits as well. Currently only E820 map is in use. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- OvmfPkg/Include/Guid/XenInfo.h | 7 +++++++ OvmfPkg/PlatformPei/Xen.h | 44

Patches before the last are small cleanups. In the last patch I'm trying to extract / generalize an idea from Stefan Hajnoczi's review of my virtio-net driver for OVMF. Unfortunately I can't find Stefan's email on any mailing list archive (sourceforge, gmane, mail-archive etc. all have only my response), so I'll quote it here. The patch Stefan was reviewing is

Patches before the last are small cleanups. In the last patch I'm trying to extract / generalize an idea from Stefan Hajnoczi's review of my virtio-net driver for OVMF. Unfortunately I can't find Stefan's email on any mailing list archive (sourceforge, gmane, mail-archive etc. all have only my response), so I'll quote it here. The patch Stefan was reviewing is

On Sat, Nov 16, 2013 at 3:31 AM, Jordan Justen <jljusten@gmail.com> wrote: > When I try to boot this on qemu or kvm, it asserts because the video > framebuffer address is NULL. > That''s expected because of the hack. ;-) > On Fri, Nov 15, 2013 at 7:58 AM, Wei Liu <wei.liu2@citrix.com> wrote: >> This is a quick hack I pulled together last night to make OVMF

Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- tools/firmware/ovmf-makefile | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/tools/firmware/ovmf-makefile b/tools/firmware/ovmf-makefile index 073ed44..efb4fb1 100644 --- a/tools/firmware/ovmf-makefile +++ b/tools/firmware/ovmf-makefile @@ -1,3 +1,6 @@ +XEN_ROOT = $(CURDIR)/../../.. +include

Hi, I migrated a physical CentOS 4.8 server into a VM on a CentOS 5 KVM host. Everything works fine, I even can use the paravirt drivers for network and disk. However the required kernel modules are not put into initrd somehow. Of course I can call "mkinitrd --with virtioblk ..." manually but that's too easy to forget. I searched the web but I didn't find any similar

On 09/09/20 10:27, Ard Biesheuvel wrote: > (adding Laszlo and Brijesh) > > On Tue, 8 Sep 2020 at 20:46, Borislav Petkov <bp at alien8.de> wrote: >> >> + Ard so that he can ack the efi bits. >> >> On Mon, Sep 07, 2020 at 03:16:12PM +0200, Joerg Roedel wrote: >>> From: Tom Lendacky <thomas.lendacky at amd.com> >>> >>> Calling

Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- tools/firmware/ovmf-makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/firmware/ovmf-makefile b/tools/firmware/ovmf-makefile index c3cd466..073ed44 100644 --- a/tools/firmware/ovmf-makefile +++ b/tools/firmware/ovmf-makefile @@ -10,7 +10,7

> It is a "generic example" which differs from the "actual example" on Fedora. ;) > Someone may favor wiki style, then again someone graces the source doc style. > What is important, none of them is a redundant, that is, they complement each other. > Patching for Fedora (or for whichever other distro) in upstream Syslinux should only be done when it would affect

On 07.03.2016 19:24, Ady via Syslinux wrote: >> doc: keytab-lilo example on Fedora >> >> --- >> doc/keytab-lilo.txt | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/doc/keytab-lilo.txt b/doc/keytab-lilo.txt >> index cdbea0f..f35b3e8 100644 >> --- a/doc/keytab-lilo.txt >> +++ b/doc/keytab-lilo.txt >> @@ -83,3 +83,7 @@

On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote: > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > > Hi Michael, > > > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > > you added a new feature bit (VIRTIO_F_IOMMU_PLATFORM) to describe whether > > or not a given virtio device requires

On Mon, Oct 10, 2016 at 05:59:03PM +0100, Will Deacon wrote: > On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > > > Hi Michael, > > > > > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > > > you added a new feature bit

On Mon, Oct 10, 2016 at 05:59:03PM +0100, Will Deacon wrote: > On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > > > Hi Michael, > > > > > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > > > you added a new feature bit

On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > Hi Michael, > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > you added a new feature bit (VIRTIO_F_IOMMU_PLATFORM) to describe whether > or not a given virtio device requires physical address or bus addresses. > > Is there a plan to get this incorporated into the virtio

On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > Hi Michael, > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > you added a new feature bit (VIRTIO_F_IOMMU_PLATFORM) to describe whether > or not a given virtio device requires physical address or bus addresses. > > Is there a plan to get this incorporated into the virtio

Rename the bit to match latest virtio spec. Add a compat macro to avoid breaking existing userspace. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- arch/um/drivers/virtio_uml.c | 2 +- drivers/vdpa/ifcvf/ifcvf_base.h | 2 +- drivers/vdpa/vdpa_sim/vdpa_sim.c | 4 ++-- drivers/vhost/net.c | 4 ++-- drivers/vhost/vdpa.c | 2 +-