All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, "Nguyen,
	Tom L" <tom.l.nguyen@intel.com>,
	"Brainard, Jim" <jim.brainard@hp.com>,
	"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>
Subject: Re: PME_Turn_Off in Linux
Date: Wed, 17 Jan 2007 13:33:18 -0800	[thread overview]
Message-ID: <20070117213318.GA2525@kroah.com> (raw)
In-Reply-To: <E717642AF17E744CA95C070CA815AE550116B7C8@cceexc23.americas.cpqcorp.net>

On Wed, Jan 17, 2007 at 10:43:14AM -0600, Miller, Mike (OS Dev) wrote:
> Hello,
> We've been seeing some nasty data corruption issues on some platforms.
> We've been capturing PCI-E traces looking for something nasty but we
> haven't found anything yet. One of the hardware guys if asking if there
> is a call in Linux to issue a PME_Turn_Off broadcast message.
>  
> PME_Turn_Off Broadcast Message
> Before main component power and reference clocks are turned off, the
> Root Complex or Switch Downstream Port must issue a broadcast Message
> that instructs all agents downstream of that point within the hierarchy
> to cease initiation of any subsequent PM_PME Messages, effective
> immediately upon receipt of the PME_Turn_Off Message.
> 
> This must be initiated from the root complex. Is there such a call in
> linux?

This firmware that implements the PCI-E connection should do this, I
don't think there is anything that the Operating system can do to
control this, as PCI-E should be transparant to the OS.

Unless this is on a PCI-E Hotplug system?  What is the sequence of
events that cause the data corruption?

thanks,

greg k-h

  reply	other threads:[~2007-01-17 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 16:43 PME_Turn_Off in Linux Miller, Mike (OS Dev)
2007-01-17 21:33 ` Greg KH [this message]
2007-01-17 22:35   ` Miller, Mike (OS Dev)
2007-01-17 22:55     ` 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=20070117213318.GA2525@kroah.com \
    --to=greg@kroah.com \
    --cc=Mike.Miller@hp.com \
    --cc=andrew.patterson@hp.com \
    --cc=jim.brainard@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tom.l.nguyen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.