mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maran Wilson <maran.wilson@oracle.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, xen-devel@lists.xenproject.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	pbonzini@redhat.com, jgross@suse.com, boris.ostrovsky@oracle.com,
	bp@suse.de, dave.hansen@linux.intel.com, davem@davemloft.net,
	gregkh@linuxfoundation.org, hpa@zytor.com, jpoimboe@redhat.com,
	kirill.shutemov@linux.intel.com, luto@kernel.org,
	mchehab@kernel.org, mingo@redhat.com, rdunlap@infradead.org,
	tglx@linutronix.de, thomas.lendacky@amd.com, hch@infradead.org,
	roger.pau@citrix.com, rkrcmar@redhat.com
Subject: Re: [PATCH v9 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Wed, 12 Dec 2018 13:56:17 -0800	[thread overview]
Message-ID: <8483ef47-cd95-8d73-0a2f-2a65d262e2d9@oracle.com> (raw)
In-Reply-To: <20181212203901.GI6653@zn.tnic>



On 12/12/2018 12:39 PM, Borislav Petkov wrote:
> On Tue, Dec 11, 2018 at 11:29:21AM -0800, Maran Wilson wrote:
>> Is your question about what options you need to provide to Qemu? Or is your
>> question about the SW implementation choices?
>>
>> Assuming the former...
> Yeah, that's what I wanted to know. But looking at it, I'm booting
> bzImage here just as quickly and as flexible so I don't see the
> advantage of this new method for my use case here of booting kernels
> in qemu.
>
> But maybe there's a good use case where firmware is slow and one doesn't
> really wanna noodle through it or when one does start a gazillion VMs
> per second or whatever...

Right, the time saved is not something you would notice while starting a 
VM manually. But it does reduce the time to reach startup_64() in Linux 
by about 50% (going from around 94ms to around 47ms) when booting a VM 
using Qemu+qboot (for example). That time savings becomes pretty 
important when you are trying to use VMs as containers (for instance, as 
is the case with Kata containers) and trying to get the latency for 
launching such a container really low -- to come as close as possible to 
match the latency for launching more traditional containers that don't 
have the additional security/isolation of running within a separate VM.

Thanks,
-Maran

>
> Thx.
>


  reply	other threads:[~2018-12-12 21:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 19:05 Maran Wilson
2018-12-10 19:07 ` [PATCH v9 1/7] xen/pvh: Split CONFIG_XEN_PVH into CONFIG_PVH and CONFIG_XEN_PVH Maran Wilson
2018-12-11 13:22   ` Borislav Petkov
2018-12-10 19:07 ` [PATCH v9 2/7] xen/pvh: Move PVH entry code out of Xen specific tree Maran Wilson
2018-12-10 19:08 ` [PATCH v9 3/7] xen/pvh: Create a new file for Xen specific PVH code Maran Wilson
2018-12-10 19:08 ` [PATCH v9 4/7] xen/pvh: Move Xen specific PVH VM initialization out of common file Maran Wilson
2018-12-10 19:08 ` [PATCH v9 5/7] xen/pvh: Move Xen code for getting mem map via hcall " Maran Wilson
2018-12-10 19:09 ` [PATCH v9 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2018-12-10 19:09 ` [PATCH v9 7/7] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2018-12-11 13:18 ` [PATCH v9 0/7] " Borislav Petkov
2018-12-11 19:29   ` Maran Wilson
2018-12-12 20:39     ` Borislav Petkov
2018-12-12 21:56       ` Maran Wilson [this message]
2018-12-13 13:15       ` Paolo Bonzini
2018-12-14 23:13 ` Boris Ostrovsky

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=8483ef47-cd95-8d73-0a2f-2a65d262e2d9@oracle.com \
    --to=maran.wilson@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=jpoimboe@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rkrcmar@redhat.com \
    --cc=roger.pau@citrix.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®