From: Michael Ellerman <michael@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: kexec@lists.infradead.org, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc,kexec: Speedup kexec hpte tear down
Date: Wed, 12 May 2010 11:36:11 +1000 [thread overview]
Message-ID: <1273628171.5738.36.camel@concordia> (raw)
In-Reply-To: <9537.1273626418@neuling.org>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Wed, 2010-05-12 at 11:06 +1000, Michael Neuling wrote:
> > > We probably only do the remove on < 1% of the hptes now. So I doubt we
> > > would get a speedup since most of the time we aren't do the remove
> > > anymore.
> >
> > It would be nice to have some actual numbers. Could you add some
> > counters and print the results at the end? (Or don't you have any
> > way to print things at that stage?)
>
> Printing is hard at that point but I think we can do it. I'll try to
> when I get some time.
A version of udbg_putcLP() that uses a raw hcall should work, or there
was code added to purgatory recently to print to the HV console which
you could nick.
> A heavily loaded system which kdumps will need a lot more hptes removes
> than kexec, so stats for both these cases might be useful also.
Yeah, or even a system that is kexec'ed while lots of stuff is still
running.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-05-12 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 6:28 [PATCH 1/2] powerpc: Add hcall to read 4 ptes at a time in real mode Michael Neuling
2010-05-11 6:28 ` [PATCH 2/2] powerpc,kexec: Speedup kexec hpte tear down Michael Neuling
2010-05-11 7:04 ` Michael Ellerman
2010-05-11 23:29 ` Michael Neuling
2010-05-12 0:36 ` Michael Ellerman
2010-05-12 0:43 ` Michael Neuling
2010-05-12 1:00 ` Paul Mackerras
2010-05-12 1:06 ` Michael Neuling
2010-05-12 1:36 ` Michael Ellerman [this message]
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=1273628171.5738.36.camel@concordia \
--to=michael@ellerman.id.au \
--cc=anton@samba.org \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=paulus@samba.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).