From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, paulus@samba.org
Subject: Re: [POWERPC] merge iSeries i/o operations with the rest
Date: Mon, 04 Sep 2006 22:07:50 -0700 [thread overview]
Message-ID: <1157432871.2413.9.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20060905120817.e52857ee.sfr@canb.auug.org.au>
On Tue, 2006-09-05 at 12:08 +1000, Stephen Rothwell wrote:
> The low level i/o operations are now handled in iSeires by taking a
> trap when we access the (inaccessible) io memory region and calling
> the Hypervisor from the trap code.
There was some discussion of the possibility of using the 'alternatives'
mechanism to patch the I/O instructions at run-time when we find we've
booted on iSeries -- just turning each one into a jump to a trampoline
which does the appropriate hypervisor calls, thus avoiding the overhead
of the trap each time.
Was that approach not viable, or not noticeably less of a performance
hit on iSeries?
--
dwmw2
next prev parent reply other threads:[~2006-09-05 5:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 2:08 [POWERPC] merge iSeries i/o operations with the rest Stephen Rothwell
2006-09-05 5:07 ` David Woodhouse [this message]
2006-09-05 5:39 ` Stephen Rothwell
2006-09-05 16:41 ` Linas Vepstas
2006-09-05 23:19 ` Stephen Rothwell
2006-09-06 8:24 ` Stephen Rothwell
2006-09-18 5:38 ` Stephen Rothwell
2006-09-20 12:15 ` Stephen Rothwell
2006-09-20 16:01 ` Hollis Blanchard
2006-09-21 0:03 ` Stephen Rothwell
2006-09-21 0:20 ` Michael Ellerman
2006-09-21 4:55 ` [POWERPC] mark BUG() as noreturn Stephen Rothwell
2006-09-21 12:18 ` Jimi Xenidis
2006-09-22 0:54 ` Michael Ellerman
2006-09-22 1:34 ` Amos Waterland
2006-09-22 10:58 ` Jimi Xenidis
2006-09-21 13:23 ` David Howells
2006-09-21 15:15 ` Segher Boessenkool
2006-09-21 8:00 ` [POWERPC] merge iSeries i/o operations with the rest Stephen Rothwell
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=1157432871.2413.9.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).