Skip to contentSkip to conversation

x86, mce: Make xeon75xx memory driver dependent on PCI

tip:x86/mce Mauro Carvalho Chehab 1 participant 1 message Feb 20, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 211660974.2010861266660371958.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com

#1 lore raw

----- "Andi Kleen" <[email protected]> escreveu:

Quoted 12 lines

On Fri, Feb 19, 2010 at 10:14:17PM -0200, Mauro Carvalho Chehab wrote:

Mauro,

Quoted 1 line

I was thinking on a way where we could work with the EDAC/MCE

issues, and

Quoted 1 line

a way for us to move ahead. My proposal is to organize an EDAC/MCE

BoF session

Quoted 1 line

or a mini-summit during the Collaboration Summit, in San Francisco,

with

Quoted 1 line

the interested parties. I suspect that some of us will be there

Quoted 8 lines

already.

I didn't plan to be there so far. A BoF is probably a good idea, and also looking closely at EDAC together,
but it would be better at some more kernel focussed conference.

If everyone else is at that summit I can try to come, but it would be likely difficult.

I'm proposing the Collaboration Summit due to its date: it will happen in April. The next Kernel conf will be on a longer time.

Quoted 2 lines

We could probably do some kind of online BoF shorter time (e.g. using some chat setup or on the phone)

We may try to do some discussions via chat before it, but I still think that having we all at the same room with some whiteboard will better work.

Quoted 8 lines
Quoted 1 line

It shouldn't be hard to find some place there for us to take a look

at the

Quoted 1 line

EDAC architecture and come with some proposal.

Proposal for what exactly?

Is this for a event interface or for a topology interface or both or something else entirely?

We should define the topics. I think we should discuss both topics. I agree that the better is to represent the hardware per FRU. So, maybe we can find a better topology representation.

Quoted 4 lines

My personal plan so far was to work on the APEI interface and then possibly look at migrating MCE to that infrastructure too, while updating mcelog to talk to it. This would be mostly addressing events so far.

The better is to have some discussions before using APEI or any other interface for it. It should be considered that the hardware errors should be presented on a consistent way not only for newer processors and memory controllers, but also for the already supported ones.

Quoted 8 lines
Quoted 1 line

As today is the last day for CFP, I've also submitted there a

proposal for a

Quoted 1 line

panel. If approved, we can use it to collect data from hardware

error users

Quoted 1 line

(sysops and other users that require high availability on their

services),

Quoted 1 line

for us to discuss some strategies to address the issue or to

summarize what

Quoted 8 lines
Quoted 1 line

will be discussed on the event.

You want to collect error rates or want to collect use cases?

For a serious collection doing it online would probably give better coverage.

I do both to some degree already.

Both data collect are important (and I also do it to some degree), and we can do it via other means, but a face-to-face meeting may help to vallidate any ideas we may have about improvements/changes at the interfaces and features.

If we succeed on such discussions at the planning phase, this will save us a lot of development time and will help to have an easier upstream adoption.

So, I think it is a worthy try.

Cheers,
Mauro