mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Paalanen <pq@iki.fi>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <srostedt@redhat.com>,
	proski@gnu.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] x86: fix mmiotrace 8-bit register decoding
Date: Sat, 26 Jul 2008 17:55:57 +0200	[thread overview]
Message-ID: <20080726155557.GA10224@elte.hu> (raw)
In-Reply-To: <20080722220035.0c193738@ct200006>


* Pekka Paalanen <pq@iki.fi> wrote:

> From 8321edde04244cc91470da5a7a71b79b704b0da1 Mon Sep 17 00:00:00 2001
> From: Pekka Paalanen <pq@iki.fi>
> Date: Mon, 21 Jul 2008 18:49:56 +0300
> Subject: [PATCH] x86: fix mmiotrace 8-bit register decoding
> 
> When SIL, DIL, BPL or SPL registers were used in MMIO, the datum
> was extracted from AH, BH, CH, or DH, which are incorrect.
> 
> Signed-off-by: Pekka Paalanen <pq@iki.fi>
> ---
> 
> This patch was cooked in Linus' tree because I couldn't get linux-next 
> to boot properly at the time. It applies cleanly to tip/master though. 
> Another problem I noticed is with non-page-aligned mappings, but 
> that's a different story.

applied to tip/tracing/mmiotrace - thanks Pekka!

	Ingo

  reply	other threads:[~2008-07-26 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080628214626.5f9199d7@daedalus.pq.iki.fi>
     [not found] ` <20080630123736.GA4011@elte.hu>
2008-06-30 20:48   ` mmiotrace broken in linux-next (8-bit writes only) Pekka Paalanen
2008-06-30 21:41     ` Vegard Nossum
2008-07-22 19:00       ` [PATCH] x86: fix mmiotrace 8-bit register decoding Pekka Paalanen
2008-07-26 15:55         ` Ingo Molnar [this message]
2008-07-01  8:15     ` mmiotrace broken in linux-next (8-bit writes only) Ingo Molnar

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=20080726155557.GA10224@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=pq@iki.fi \
    --cc=proski@gnu.org \
    --cc=srostedt@redhat.com \
    --cc=vegard.nossum@gmail.com \
    /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

Powered by JetHome