From: Sean Christopherson <seanjc@google.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, aleksandar.qemu.devel@gmail.com,
alexandru.elisei@arm.com, anup.patel@wdc.com,
aou@eecs.berkeley.edu, atish.patra@wdc.com,
borntraeger@linux.ibm.com, bp@alien8.de, catalin.marinas@arm.com,
chenhuacai@kernel.org, dave.hansen@linux.intel.com,
frankja@linux.ibm.com, frederic@kernel.org, gor@linux.ibm.com,
hca@linux.ibm.com, james.morse@arm.com, jmattson@google.com,
joro@8bytes.org, luto@kernel.org, maz@kernel.org,
mingo@redhat.com, mpe@ellerman.id.au, nsaenzju@redhat.com,
palmer@dabbelt.com, paulmck@kernel.org, paul.walmsley@sifive.com,
peterz@infradead.org, suzuki.poulose@arm.com,
svens@linux.ibm.com, tglx@linutronix.de,
tsbogend@alpha.franken.de, vkuznets@redhat.com,
wanpengli@tencent.com, will@kernel.org
Subject: Re: [PATCH v2 4/7] kvm/mips: rework guest entry logic
Date: Thu, 20 Jan 2022 17:17:48 +0000 [thread overview]
Message-ID: <YemZPAgGsbiUokZk@google.com> (raw)
In-Reply-To: <20220120171551.GB15464@C02TD0UTHF1T.local>
On Thu, Jan 20, 2022, Mark Rutland wrote:
> Longer-term MIPS should move to a loop like everyone else has:
>
> for (;;) {
> status = kvm_mips_enter_exit_vcpu();
>
> if (handle_exit(status))
> break;
>
> ...
> }
>
> ... which is far easier to manage.
I don't suppose we can just remove MIPS "support"? And PPC while we're at it? :-D
next prev parent reply other threads:[~2022-01-20 17:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 10:58 [PATCH v2 0/7] kvm: fix latent guest entry/exit bugs Mark Rutland
2022-01-19 10:58 ` [PATCH v2 1/7] entry: add arch_in_rcu_eqs() Mark Rutland
2022-01-19 17:35 ` Christian Borntraeger
2022-01-21 17:34 ` Nicolas Saenz Julienne
2022-01-19 10:58 ` [PATCH v2 2/7] kvm: add guest_state_{enter,exit}_irqoff() Mark Rutland
2022-01-20 11:00 ` Paolo Bonzini
2022-01-21 17:35 ` Nicolas Saenz Julienne
2022-01-19 10:58 ` [PATCH v2 3/7] kvm/arm64: rework guest entry logic Mark Rutland
2022-01-21 17:37 ` Nicolas Saenz Julienne
2022-01-19 10:58 ` [PATCH v2 4/7] kvm/mips: " Mark Rutland
2022-01-20 11:10 ` Paolo Bonzini
2022-01-20 13:33 ` Mark Rutland
2022-01-20 16:44 ` Mark Rutland
2022-01-20 16:57 ` Paolo Bonzini
2022-01-20 17:15 ` Mark Rutland
2022-01-20 17:17 ` Sean Christopherson [this message]
2022-01-20 17:29 ` Paolo Bonzini
2022-01-21 12:44 ` Mark Rutland
2022-01-19 10:58 ` [PATCH v2 5/7] kvm/riscv: " Mark Rutland
2022-01-20 11:18 ` Paolo Bonzini
2022-01-20 12:56 ` Mark Rutland
2022-01-20 13:13 ` Paolo Bonzini
2022-01-19 10:58 ` [PATCH v2 6/7] kvm/s390: " Mark Rutland
2022-01-19 10:58 ` [PATCH v2 7/7] kvm/x86: " Mark Rutland
2022-01-20 11:20 ` Paolo Bonzini
2022-01-21 17:40 ` Nicolas Saenz Julienne
2022-01-19 18:25 ` [PATCH v2 0/7] kvm: fix latent guest entry/exit bugs Christian Borntraeger
2022-01-19 18:28 ` Christian Borntraeger
2022-01-19 19:22 ` Mark Rutland
2022-01-19 19:30 ` Christian Borntraeger
2022-01-20 11:57 ` Mark Rutland
2022-01-20 12:02 ` Christian Borntraeger
2022-01-20 11:28 ` Paolo Bonzini
2022-01-20 12:03 ` Mark Rutland
2022-01-20 15:14 ` Christian Borntraeger
2022-01-21 9:53 ` Christian Borntraeger
2022-01-21 14:17 ` Christian Borntraeger
2022-01-21 14:30 ` Mark Rutland
2022-01-21 14:42 ` Christian Borntraeger
2022-01-21 15:29 ` Mark Rutland
2022-01-21 15:40 ` Christian Borntraeger
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=YemZPAgGsbiUokZk@google.com \
--to=seanjc@google.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=alexandru.elisei@arm.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=frankja@linux.ibm.com \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=james.morse@arm.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nsaenzju@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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.