From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Michael Tokarev <mjt@tls.msk.ru>, Julio Guerra <julio@farjump.io>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
qemu-trivial@nongnu.org
Cc: christophe@farjump.io, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v2] taget-ppc: Fix read access to IBAT registers higher than IBAT3
Date: Tue, 03 Nov 2015 13:29:32 +0000 [thread overview]
Message-ID: <5638B6BC.50000@ilande.co.uk> (raw)
In-Reply-To: <5638A5AF.9000709@msgid.tls.msk.ru>
On 03/11/15 12:16, Michael Tokarev wrote:
> 03.11.2015 11:00, Julio Guerra wrote:
>> Ping :)
>
> Well, I'm not sure what can I do with this. I've no idea what is IBAT to start
> with, so while technically the patch is a one-liner, I've no idea what it does
> and how trivial it is :)
>
> Maybe you can include some context which teaches me what it is all about, and in
> that case it becomes really trivial, or.. I dunno :)
FWIW PPC has a set of IBAT and DBAT registers on chip, each of which
indicates a large continuous physical/virtual memory mapping for
Instruction and Data memory respectively. The idea is that the OS can
use these to provide "fast" virtual to physical lookups instead of
invoking a time-consuming hash lookup to provide the translation.
From casual observation comparing with spr_write_ibatu_h() in the same
file (which already includes the +4 offset that the patch is adding to
spr_read_ibat_h()), it does look like a genuine bug. However it really
needs someone who understands PPC architecture a bit more to give a RB
to ensure this is doing the right thing.
ATB,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Michael Tokarev <mjt@tls.msk.ru>, Julio Guerra <julio@farjump.io>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
qemu-trivial@nongnu.org
Cc: christophe@farjump.io, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] taget-ppc: Fix read access to IBAT registers higher than IBAT3
Date: Tue, 03 Nov 2015 13:29:32 +0000 [thread overview]
Message-ID: <5638B6BC.50000@ilande.co.uk> (raw)
In-Reply-To: <5638A5AF.9000709@msgid.tls.msk.ru>
On 03/11/15 12:16, Michael Tokarev wrote:
> 03.11.2015 11:00, Julio Guerra wrote:
>> Ping :)
>
> Well, I'm not sure what can I do with this. I've no idea what is IBAT to start
> with, so while technically the patch is a one-liner, I've no idea what it does
> and how trivial it is :)
>
> Maybe you can include some context which teaches me what it is all about, and in
> that case it becomes really trivial, or.. I dunno :)
FWIW PPC has a set of IBAT and DBAT registers on chip, each of which
indicates a large continuous physical/virtual memory mapping for
Instruction and Data memory respectively. The idea is that the OS can
use these to provide "fast" virtual to physical lookups instead of
invoking a time-consuming hash lookup to provide the translation.
>From casual observation comparing with spr_write_ibatu_h() in the same
file (which already includes the +4 offset that the patch is adding to
spr_read_ibat_h()), it does look like a genuine bug. However it really
needs someone who understands PPC architecture a bit more to give a RB
to ensure this is doing the right thing.
ATB,
Mark.
next prev parent reply other threads:[~2015-11-03 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 17:43 [Qemu-trivial] [PATCH v2] taget-ppc: Fix read access to IBAT registers higher than IBAT3 Julio Guerra
2015-10-14 17:43 ` [Qemu-devel] " Julio Guerra
2015-11-03 8:00 ` [Qemu-trivial] " Julio Guerra
2015-11-03 8:00 ` [Qemu-devel] " Julio Guerra
2015-11-03 12:16 ` [Qemu-trivial] " Michael Tokarev
2015-11-03 12:16 ` [Qemu-devel] " Michael Tokarev
2015-11-03 13:29 ` Mark Cave-Ayland [this message]
2015-11-03 13:29 ` Mark Cave-Ayland
2015-11-03 16:52 ` [Qemu-trivial] " Julio Guerra
2015-11-03 16:52 ` Julio Guerra
2015-11-06 8:04 ` [Qemu-trivial] " Michael Tokarev
2015-11-06 8:04 ` [Qemu-devel] " Michael Tokarev
2015-11-11 1:03 ` [Qemu-trivial] [Qemu-ppc] " David Gibson
2015-11-11 1:03 ` [Qemu-devel] " David Gibson
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=5638B6BC.50000@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=agraf@suse.de \
--cc=christophe@farjump.io \
--cc=julio@farjump.io \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.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.