From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
will@kernel.org, catalin.marinas@arm.com, james.morse@arm.com,
suzuki.poulose@arm.com, drjones@redhat.com,
eric.auger@redhat.com, aarcange@redhat.com, shan.gavin@gmail.com
Subject: Re: [PATCH RFCv2 0/9] kvm/arm64: Support Async Page Fault
Date: Wed, 27 May 2020 08:48:27 +0100 [thread overview]
Message-ID: <ae0f32fa338969d25dc3da56292e35ed@kernel.org> (raw)
In-Reply-To: <987785b2-2533-c3d8-8f6a-4193aa82d502@redhat.com>
On 2020-05-27 03:39, Gavin Shan wrote:
> Hi Mark,
[...]
>> Can you run tests with a real workload? For example, a kernel build
>> inside the VM?
>>
>
> Yeah, I agree it's far from a realistic workload. However, it's the
> test case
> which was suggested when async page fault was proposed from day one,
> according
> to the following document. On the page#34, you can see the benchmark,
> which is
> similar to what we're doing.
>
> https://www.linux-kvm.org/images/a/ac/2010-forum-Async-page-faults.pdf
My own question is whether this even makes any sense 10 years later.
The HW has massively changed, and this adds a whole lot of complexity
to both the hypervisor and the guest. It also plays very ugly games
with the exception model, which doesn't give me the warm fuzzy feeling
that it's going to be great.
> Ok. I will test with the workload to build kernel or another better one
> to
> represent the case.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
shan.gavin@gmail.com, pbonzini@redhat.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFCv2 0/9] kvm/arm64: Support Async Page Fault
Date: Wed, 27 May 2020 08:48:27 +0100 [thread overview]
Message-ID: <ae0f32fa338969d25dc3da56292e35ed@kernel.org> (raw)
In-Reply-To: <987785b2-2533-c3d8-8f6a-4193aa82d502@redhat.com>
On 2020-05-27 03:39, Gavin Shan wrote:
> Hi Mark,
[...]
>> Can you run tests with a real workload? For example, a kernel build
>> inside the VM?
>>
>
> Yeah, I agree it's far from a realistic workload. However, it's the
> test case
> which was suggested when async page fault was proposed from day one,
> according
> to the following document. On the page#34, you can see the benchmark,
> which is
> similar to what we're doing.
>
> https://www.linux-kvm.org/images/a/ac/2010-forum-Async-page-faults.pdf
My own question is whether this even makes any sense 10 years later.
The HW has massively changed, and this adds a whole lot of complexity
to both the hypervisor and the guest. It also plays very ugly games
with the exception model, which doesn't give me the warm fuzzy feeling
that it's going to be great.
> Ok. I will test with the workload to build kernel or another better one
> to
> represent the case.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
aarcange@redhat.com, drjones@redhat.com, suzuki.poulose@arm.com,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
eric.auger@redhat.com, james.morse@arm.com, shan.gavin@gmail.com,
pbonzini@redhat.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFCv2 0/9] kvm/arm64: Support Async Page Fault
Date: Wed, 27 May 2020 08:48:27 +0100 [thread overview]
Message-ID: <ae0f32fa338969d25dc3da56292e35ed@kernel.org> (raw)
In-Reply-To: <987785b2-2533-c3d8-8f6a-4193aa82d502@redhat.com>
On 2020-05-27 03:39, Gavin Shan wrote:
> Hi Mark,
[...]
>> Can you run tests with a real workload? For example, a kernel build
>> inside the VM?
>>
>
> Yeah, I agree it's far from a realistic workload. However, it's the
> test case
> which was suggested when async page fault was proposed from day one,
> according
> to the following document. On the page#34, you can see the benchmark,
> which is
> similar to what we're doing.
>
> https://www.linux-kvm.org/images/a/ac/2010-forum-Async-page-faults.pdf
My own question is whether this even makes any sense 10 years later.
The HW has massively changed, and this adds a whole lot of complexity
to both the hypervisor and the guest. It also plays very ugly games
with the exception model, which doesn't give me the warm fuzzy feeling
that it's going to be great.
> Ok. I will test with the workload to build kernel or another better one
> to
> represent the case.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-27 7:48 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 3:29 [PATCH RFCv2 0/9] kvm/arm64: Support Async Page Fault Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 1/9] arm64: Probe for the presence of KVM hypervisor services during boot Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 2/9] arm/arm64: KVM: Advertise KVM UID to guests via SMCCC Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 3/9] kvm/arm64: Rename kvm_vcpu_get_hsr() to kvm_vcpu_get_esr() Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 10:42 ` Mark Rutland
2020-05-26 10:42 ` Mark Rutland
2020-05-26 10:42 ` Mark Rutland
2020-05-27 2:43 ` Gavin Shan
2020-05-27 2:43 ` Gavin Shan
2020-05-27 2:43 ` Gavin Shan
2020-05-27 7:20 ` Marc Zyngier
2020-05-27 7:20 ` Marc Zyngier
2020-05-27 7:20 ` Marc Zyngier
2020-05-28 6:34 ` Gavin Shan
2020-05-28 6:34 ` Gavin Shan
2020-05-28 6:34 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 4/9] kvm/arm64: Detach ESR operator from vCPU struct Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 10:51 ` Mark Rutland
2020-05-26 10:51 ` Mark Rutland
2020-05-26 10:51 ` Mark Rutland
2020-05-27 2:55 ` Gavin Shan
2020-05-27 2:55 ` Gavin Shan
2020-05-27 2:55 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 5/9] kvm/arm64: Replace hsr with esr Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 10:45 ` Mark Rutland
2020-05-26 10:45 ` Mark Rutland
2020-05-26 10:45 ` Mark Rutland
2020-05-27 2:56 ` Gavin Shan
2020-05-27 2:56 ` Gavin Shan
2020-05-27 2:56 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 6/9] kvm/arm64: Export kvm_handle_user_mem_abort() with prefault mode Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 10:58 ` Mark Rutland
2020-05-26 10:58 ` Mark Rutland
2020-05-26 10:58 ` Mark Rutland
2020-05-27 3:01 ` Gavin Shan
2020-05-27 3:01 ` Gavin Shan
2020-05-27 3:01 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 7/9] kvm/arm64: Support async page fault Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 12:34 ` Mark Rutland
2020-05-26 12:34 ` Mark Rutland
2020-05-26 12:34 ` Mark Rutland
2020-05-27 4:05 ` Gavin Shan
2020-05-27 4:05 ` Gavin Shan
2020-05-27 4:05 ` Gavin Shan
2020-05-27 7:37 ` Marc Zyngier
2020-05-27 7:37 ` Marc Zyngier
2020-05-27 7:37 ` Marc Zyngier
2020-05-28 6:32 ` Gavin Shan
2020-05-28 6:32 ` Gavin Shan
2020-05-28 6:32 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 8/9] kernel/sched: Add cpu_rq_is_locked() Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` [PATCH RFCv2 9/9] arm64: Support async page fault Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-08 3:29 ` Gavin Shan
2020-05-26 12:56 ` Mark Rutland
2020-05-26 12:56 ` Mark Rutland
2020-05-26 12:56 ` Mark Rutland
2020-05-27 6:48 ` Paolo Bonzini
2020-05-27 6:48 ` Paolo Bonzini
2020-05-27 6:48 ` Paolo Bonzini
2020-05-28 6:14 ` Gavin Shan
2020-05-28 6:14 ` Gavin Shan
2020-05-28 6:14 ` Gavin Shan
2020-05-28 7:03 ` Marc Zyngier
2020-05-28 7:03 ` Marc Zyngier
2020-05-28 7:03 ` Marc Zyngier
2020-05-28 10:53 ` Paolo Bonzini
2020-05-28 10:53 ` Paolo Bonzini
2020-05-28 10:53 ` Paolo Bonzini
2020-05-28 10:48 ` Paolo Bonzini
2020-05-28 10:48 ` Paolo Bonzini
2020-05-28 10:48 ` Paolo Bonzini
2020-05-28 23:02 ` Gavin Shan
2020-05-28 23:02 ` Gavin Shan
2020-05-28 23:02 ` Gavin Shan
2020-05-29 9:41 ` Marc Zyngier
2020-05-29 9:41 ` Marc Zyngier
2020-05-29 9:41 ` Marc Zyngier
2020-05-29 11:11 ` Paolo Bonzini
2020-05-29 11:11 ` Paolo Bonzini
2020-05-29 11:11 ` Paolo Bonzini
2020-05-31 12:44 ` Marc Zyngier
2020-05-31 12:44 ` Marc Zyngier
2020-05-31 12:44 ` Marc Zyngier
2020-06-01 9:21 ` Paolo Bonzini
2020-06-01 9:21 ` Paolo Bonzini
2020-06-01 9:21 ` Paolo Bonzini
2020-06-02 5:44 ` Gavin Shan
2020-06-02 5:44 ` Gavin Shan
2020-06-02 5:44 ` Gavin Shan
2020-05-25 23:39 ` [PATCH RFCv2 0/9] kvm/arm64: Support Async Page Fault Gavin Shan
2020-05-25 23:39 ` Gavin Shan
2020-05-25 23:39 ` Gavin Shan
2020-05-26 13:09 ` Mark Rutland
2020-05-26 13:09 ` Mark Rutland
2020-05-26 13:09 ` Mark Rutland
2020-05-27 2:39 ` Gavin Shan
2020-05-27 2:39 ` Gavin Shan
2020-05-27 2:39 ` Gavin Shan
2020-05-27 7:48 ` Marc Zyngier [this message]
2020-05-27 7:48 ` Marc Zyngier
2020-05-27 7:48 ` Marc Zyngier
2020-05-27 16:10 ` Paolo Bonzini
2020-05-27 16:10 ` Paolo Bonzini
2020-05-27 16:10 ` Paolo Bonzini
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=ae0f32fa338969d25dc3da56292e35ed@kernel.org \
--to=maz@kernel.org \
--cc=aarcange@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pbonzini@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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 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.