public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64_mca_cpe_int_handler
Date: Wed, 27 Feb 2008 10:06:31 +0000	[thread overview]
Message-ID: <47C53627.5000209@bull.net> (raw)
In-Reply-To: <47BF02EC.4080102@bull.net>

Russ,

Thank you for your remarks.

I want to add a new mechanism for the MCA/INIT handlers to be able to
store their logs in a safe way. (No locks, no waiting,...)
This will be based on the two buffers and the atomic counter for each
of the MCA/INIT handlers.

And I want to keep the existing mechanism when we are not in MCA/INIT
handlers' contexts.

Using separate mechanisms, avoids MCA/INIT handlers interfering with
the interrupts and the polling.

Should we receive too many CPEIs / CMCIs, chaining into polling,
may make us lose events.

Should we receive too many recovered MCAs or INITs, there will
always be some logs lost. I want to keep the first and the last log.
The first one to know how it begins.
Why the last one? I've got a _feeling_ that the last one will have
accumulated consequences (whatever it is) of the preceding ones.

If they are note recovered, the game is over anyway.

I'll think it over again :-)

Thanks,

Zoltan

  parent reply	other threads:[~2008-02-27 10:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 17:14 ia64_mca_cpe_int_handler Zoltan Menyhart
2008-02-22 22:32 ` ia64_mca_cpe_int_handler Luck, Tony
2008-02-22 23:44 ` ia64_mca_cpe_int_handler Russ Anderson
2008-02-23  0:02 ` ia64_mca_cpe_int_handler Luck, Tony
2008-02-25 17:05 ` ia64_mca_cpe_int_handler Zoltan Menyhart
2008-02-26 21:01 ` ia64_mca_cpe_int_handler Russ Anderson
2008-02-27 10:06 ` Zoltan Menyhart [this message]
2008-02-27 10:53 ` ia64_mca_cpe_int_handler Robin Holt
2008-02-27 12:18 ` ia64_mca_cpe_int_handler Zoltan Menyhart
2008-02-27 16:29 ` ia64_mca_cpe_int_handler Russ Anderson

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=47C53627.5000209@bull.net \
    --to=zoltan.menyhart@bull.net \
    --cc=linux-ia64@vger.kernel.org \
    /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