From: Nadav Amit <nadav.amit@gmail.com>
To: Marc Orr <marcorr@google.com>
Cc: Varad Gautam <varad.gautam@suse.com>,
Joerg Roedel <jroedel@suse.de>, kvm list <kvm@vger.kernel.org>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Jones <drjones@redhat.com>,
bp@suse.de, "Lendacky, Thomas" <thomas.lendacky@amd.com>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
Zixuan Wang <zixuanwang@google.com>,
"Hyunwook (Wooky) Baek" <baekhw@google.com>,
Erdem Aktas <erdemaktas@google.com>,
Tom Roeder <tmroeder@google.com>
Subject: Re: [kvm-unit-tests PATCH 0/6] Initial x86_64 UEFI support
Date: Wed, 18 Aug 2021 18:42:11 -0700 [thread overview]
Message-ID: <0250F07B-AC9A-4110-B2F4-8537A40D8848@gmail.com> (raw)
In-Reply-To: <CAA03e5H6mM0z5r4knbjHDLS4svLP6WQuhC_5BnSgCyXpRZgqAQ@mail.gmail.com>
> On Aug 18, 2021, at 6:32 PM, Marc Orr <marcorr@google.com> wrote:
>
> This sounds great to us. We will also experiment with combining the
> two patchsets and report back when we have some experience with this.
> Though, please do also report back if you have an update on this
> before we do.
Just wondering (aka, my standard question): does it work on
bare-metal (putting aside tests that rely on test-devices)?
WARNING: multiple messages have this Message-ID (diff)
From: Nadav Amit <nadav.amit@gmail.com>
To: Marc Orr <marcorr@google.com>
Cc: "Lendacky, Thomas" <thomas.lendacky@amd.com>,
Andrew Jones <drjones@redhat.com>, Joerg Roedel <jroedel@suse.de>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
kvm list <kvm@vger.kernel.org>, Tom Roeder <tmroeder@google.com>,
"Hyunwook \(Wooky\) Baek" <baekhw@google.com>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Zixuan Wang <zixuanwang@google.com>,
Erdem Aktas <erdemaktas@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
bp@suse.de
Subject: Re: [kvm-unit-tests PATCH 0/6] Initial x86_64 UEFI support
Date: Wed, 18 Aug 2021 18:42:11 -0700 [thread overview]
Message-ID: <0250F07B-AC9A-4110-B2F4-8537A40D8848@gmail.com> (raw)
In-Reply-To: <CAA03e5H6mM0z5r4knbjHDLS4svLP6WQuhC_5BnSgCyXpRZgqAQ@mail.gmail.com>
> On Aug 18, 2021, at 6:32 PM, Marc Orr <marcorr@google.com> wrote:
>
> This sounds great to us. We will also experiment with combining the
> two patchsets and report back when we have some experience with this.
> Though, please do also report back if you have an update on this
> before we do.
Just wondering (aka, my standard question): does it work on
bare-metal (putting aside tests that rely on test-devices)?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-08-19 1:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 11:48 [kvm-unit-tests PATCH 0/6] Initial x86_64 UEFI support Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 1/6] x86: Build tests as PE objects for the EFI loader Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 2/6] x86: Call efi_main from _efi_pe_entry Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 3/6] x86: efi_main: Get EFI memory map and exit boot services Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 4/6] x86: efi_main: Self-relocate ELF .dynamic addresses Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 5/6] cstart64.S: x86_64 bootstrapping after exiting EFI Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-02 11:48 ` [kvm-unit-tests PATCH 6/6] x86: Disable some breaking tests for EFI and modify vmexit test Varad Gautam
2021-07-02 11:48 ` Varad Gautam via Virtualization
2021-07-12 16:29 ` [kvm-unit-tests PATCH 0/6] Initial x86_64 UEFI support Andrew Jones
2021-07-12 16:29 ` Andrew Jones
2021-08-13 18:44 ` Marc Orr
2021-08-16 7:26 ` Andrew Jones
2021-08-16 7:26 ` Andrew Jones
2021-08-17 3:41 ` Marc Orr
2021-08-17 10:49 ` Joerg Roedel
2021-08-17 10:49 ` Joerg Roedel
2021-08-18 1:52 ` Marc Orr
2021-08-18 8:38 ` Varad Gautam
2021-08-18 8:38 ` Varad Gautam via Virtualization
2021-08-19 1:32 ` Marc Orr
2021-08-19 1:42 ` Nadav Amit [this message]
2021-08-19 1:42 ` Nadav Amit
2021-08-19 1:54 ` Zixuan Wang
2021-08-19 11:36 ` Varad Gautam
2021-08-19 11:36 ` Varad Gautam via Virtualization
2021-08-20 17:29 ` Marc Orr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0250F07B-AC9A-4110-B2F4-8537A40D8848@gmail.com \
--to=nadav.amit@gmail.com \
--cc=baekhw@google.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=drjones@redhat.com \
--cc=erdemaktas@google.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=marcorr@google.com \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.com \
--cc=tmroeder@google.com \
--cc=varad.gautam@suse.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=zixuanwang@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.