From: Alexander Graf <agraf@suse.de>
To: Michael Neuling <mikey@neuling.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 2/6] KVM: PPC: Book3S PR: Emulate TIR register
Date: Wed, 30 Apr 2014 10:06:38 +0000 [thread overview]
Message-ID: <5360CB2E.50104@suse.de> (raw)
In-Reply-To: <19971.1398837074@ale.ozlabs.ibm.com>
On 30.04.14 07:51, Michael Neuling wrote:
>> In parallel to the Processor ID Register (PIR) threaded POWER8 also adds a
>> Thread ID Register (TID). Since PR KVM doesn't emulate more than one thread
> s/TID/TIR/ above
Oops :)
>
>> per core, we can just always expose 0 here.
> I'm not sure if we ever do, but if we IPI ourselves using a doorbell,
> we'll need to emulate the doorbell as well.
Yeah, we don't. I'm surprised we don't myself, but I'd rather not
implement the logic to emulate doorbells until I can easily verify it
works - which means either have a Linux guest that does doorbells or
have a test harness for kernel level test cases.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Michael Neuling <mikey@neuling.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 2/6] KVM: PPC: Book3S PR: Emulate TIR register
Date: Wed, 30 Apr 2014 12:06:38 +0200 [thread overview]
Message-ID: <5360CB2E.50104@suse.de> (raw)
In-Reply-To: <19971.1398837074@ale.ozlabs.ibm.com>
On 30.04.14 07:51, Michael Neuling wrote:
>> In parallel to the Processor ID Register (PIR) threaded POWER8 also adds a
>> Thread ID Register (TID). Since PR KVM doesn't emulate more than one thread
> s/TID/TIR/ above
Oops :)
>
>> per core, we can just always expose 0 here.
> I'm not sure if we ever do, but if we IPI ourselves using a doorbell,
> we'll need to emulate the doorbell as well.
Yeah, we don't. I'm surprised we don't myself, but I'd rather not
implement the logic to emulate doorbells until I can easily verify it
works - which means either have a Linux guest that does doorbells or
have a test harness for kernel level test cases.
Alex
next prev parent reply other threads:[~2014-04-30 10:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 16:17 [PATCH 0/6] KVM: PPC: Book3S PR: Add POWER8 support Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 1/6] KVM: PPC: Book3S PR: Ignore PMU SPRs Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-30 22:12 ` Paul Mackerras
2014-04-30 22:12 ` Paul Mackerras
2014-05-02 8:35 ` Alexander Graf
2014-05-02 8:35 ` Alexander Graf
2014-05-07 7:09 ` Paul Mackerras
2014-05-07 7:09 ` Paul Mackerras
2014-05-08 12:11 ` Alexander Graf
2014-05-08 12:11 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 2/6] KVM: PPC: Book3S PR: Emulate TIR register Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-30 5:51 ` Michael Neuling
2014-04-30 5:51 ` Michael Neuling
2014-04-30 10:06 ` Alexander Graf [this message]
2014-04-30 10:06 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 3/6] KVM: PPC: Book3S PR: Handle Facility interrupt and FSCR Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 4/6] KVM: PPC: Book3S PR: Expose TAR facility to guest Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 5/6] KVM: PPC: Book3S PR: Expose EBB registers Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-04-29 16:17 ` [PATCH 6/6] KVM: PPC: Book3S PR: Expose TM registers Alexander Graf
2014-04-29 16:17 ` Alexander Graf
2014-05-17 6:20 ` Paul Mackerras
2014-05-17 6:20 ` Paul Mackerras
2014-05-19 13:09 ` Alexander Graf
2014-05-19 13:09 ` Alexander Graf
2014-05-20 9:59 ` Paul Mackerras
2014-05-20 9:59 ` Paul Mackerras
2014-05-20 11:49 ` Alexander Graf
2014-05-20 11:49 ` Alexander Graf
2014-05-04 16:36 ` [PATCH 0/6] KVM: PPC: Book3S PR: Add POWER8 support Aneesh Kumar K.V
2014-05-04 16:48 ` Aneesh Kumar K.V
2014-05-05 11:18 ` Alexander Graf
2014-05-05 11:18 ` Alexander Graf
2014-05-05 14:38 ` Aneesh Kumar K.V
2014-05-05 14:50 ` Aneesh Kumar K.V
2014-05-05 14:42 ` Alexander Graf
2014-05-05 14:42 ` Alexander Graf
2014-05-05 14:48 ` Aneesh Kumar K.V
2014-05-05 14:48 ` Aneesh Kumar K.V
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=5360CB2E.50104@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mikey@neuling.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.