public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] PCI Express patches for 2.4.27-pre3
Date: Tue, 25 May 2004 19:14:34 +0200	[thread overview]
Message-ID: <m3smdo1lad.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1ZNBb-7QA-1@gated-at.bofh.it> (Marcelo Tosatti's message of "Tue, 25 May 2004 19:10:05 +0200")

Marcelo Tosatti <marcelo.tosatti@cyclades.com> writes:
>
> Yeap, I would prefer not to apply them at this time. For one, Arjan told
> me privately it can break XFree86 which accesses the PCI config space directly.
> Right?

Erm,no. In fact it could even fix XFree86 for that, because the way
they do it currently in user space is racy and the kernel doing it 
differently would fix that race. But I would still recommend to 
not apply it, since it is somewhat risky e.g. for triggering 
new hardware bugs and it is not really needed and would dilute the
message of freeze %) XFree86 should be fixed in user space to use the proper
access methods provided by the kernel (/proc/sys etc.) 

-Andi


  parent reply	other threads:[~2004-05-25 17:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ZuS0-1b4-15@gated-at.bofh.it>
     [not found] ` <1ZuS3-1b4-35@gated-at.bofh.it>
2004-05-24 22:21   ` [BK PATCH] PCI Express patches for 2.4.27-pre3 Andi Kleen
2004-05-24 22:40     ` Greg KH
     [not found] ` <1ZE52-8sy-15@gated-at.bofh.it>
     [not found]   ` <1ZFaF-10N-13@gated-at.bofh.it>
     [not found]     ` <1ZIrV-3xS-7@gated-at.bofh.it>
     [not found]       ` <1ZJHt-4At-33@gated-at.bofh.it>
2004-05-25 13:38         ` Andi Kleen
     [not found]         ` <1ZLpV-5YK-37@gated-at.bofh.it>
     [not found]           ` <1ZNBb-7QA-1@gated-at.bofh.it>
2004-05-25 17:14             ` Andi Kleen [this message]
2004-05-26  6:29 Durairaj, Sundarapandian
2004-05-26 13:48 ` Matthew Wilcox
2004-05-26 17:03 ` Greg KH
2004-05-26 17:30   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24 21:01 Greg KH
2004-05-24 21:02 ` Greg KH
2004-05-24 21:02   ` Greg KH
2004-05-25  6:53 ` Arjan van de Ven
2004-05-25  8:00   ` Greg KH
2004-05-25 11:32     ` Matthew Wilcox
2004-05-25 12:54       ` Marcelo Tosatti
2004-05-25 13:01         ` Arjan van de Ven
2004-05-25 13:24           ` Matthew Wilcox
2004-05-25 14:41             ` Greg KH
2004-05-26  2:49               ` Jeff Garzik
2004-05-26  4:29                 ` Greg KH
2004-05-25 14:40         ` Greg KH
2004-05-25 16:59           ` Marcelo Tosatti
2004-05-25 17:05             ` Greg KH

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=m3smdo1lad.fsf@averell.firstfloor.org \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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