From: Blue Swirl <blauwirbel@gmail.com>
To: Igor Kovalenko <igor.v.kovalenko@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc64 support TSB related MMU registers
Date: Fri, 24 Apr 2009 20:42:49 +0300 [thread overview]
Message-ID: <f43fc5580904241042n7497892fv4ee573b3bf658697@mail.gmail.com> (raw)
In-Reply-To: <b2fa41d60904231556r6523ef8agc3ffd8f1691931c9@mail.gmail.com>
On 4/24/09, Igor Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> Hi!
>
> This change allows reading ultrasparc I/D MMU TSB tag target register
> and TSB pointer register (8k and 64k).
> Linux kernel uses TSB for memory management, and with this change it
> now can use early allocation routines.
>
> I'm testing with linux-2.6.29.1 minimalistic sparc64 uniprocessor
> build, now kernel is able to start build device tree.
> Without the change kernel was not able to handle D-MMU miss while
> creating first device tree node.
> Currently it stops shortly after building device tree, trying to find
> out path to console.
Nice, though I didn't notice any visible improvement in my tests.
About the patch, there are a few problems:
- it breaks Sparc32
- commented out code is ugly
- if and else should be on the same line as '{' or '}'
- long lines should be wrapped
- in the line:
+ return (((tag_access_register & 0x1fff)<<48)|(tag_access_register >> 22));
there should be white space between ) and << and 48.
> (PS with openbios instance-to-path method fails in client interface
> call, in the same way
> it fails without loading kernel when I try invoking get-instance-path
> on stdin handle from command prompt.
> there fmove invokes memmove() with size argument looking like some
> pointer which leads to unhandled D-MMU fault)
Similar very obscure problem was fixed with PPC (r481), the bug was
with the PCI nodes.
next prev parent reply other threads:[~2009-04-24 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 22:56 [Qemu-devel] [PATCH] sparc64 support TSB related MMU registers Igor Kovalenko
2009-04-24 17:42 ` Blue Swirl [this message]
[not found] ` <b2fa41d60904242246x6b1b7177ifb973c41a3c051fb@mail.gmail.com>
[not found] ` <f43fc5580904242358k74df8bf9lc0b72c92e58a38bf@mail.gmail.com>
[not found] ` <b2fa41d60904250010m52db6db4id08b5729276faf62@mail.gmail.com>
[not found] ` <b2fa41d60904250714m3eb68cfay45ed84ff78892855@mail.gmail.com>
2009-04-25 14:17 ` Igor Kovalenko
2009-04-25 15:27 ` Blue Swirl
2009-04-26 19:24 ` Igor Kovalenko
2009-04-27 16:51 ` Blue Swirl
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=f43fc5580904241042n7497892fv4ee573b3bf658697@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=igor.v.kovalenko@gmail.com \
--cc=qemu-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).