From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Javi Merino <javi.merino@cloud.com>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [XEN PATCH v1] x86/APIC: Read Error Status Register correctly
Date: Wed, 27 Nov 2024 09:44:18 +0100 [thread overview]
Message-ID: <Z0bb4t5AIm_NJkFE@macbook> (raw)
In-Reply-To: <3270b77c005745dcf56cc833bdf3e4c703190b05.1732639041.git.javi.merino@cloud.com>
On Tue, Nov 26, 2024 at 05:06:15PM +0000, Javi Merino wrote:
> The logic to read the APIC_ESR was copied from linux in a commit from
> 2002: 4676bbf96dc8 (bitkeeper revision
> 1.2 (3ddb79c9KusG02eh7i-uXkgY0IksKA), 2002-11-20). In linux 3.14,
> this logic was fixed to follow the Intel SDM (see commit
> 60283df7ac26 (x86/apic: Read Error Status Register correctly,
> 2014-01-14) in the linux kernel). The Intel(r) 64 and IA-32
> Architectures Software Develover's Manual currently says
> in Volume 3, Section 12.5.3:
>
> Before attempt to read from the ESR, software should first write to
> it. (The value written does not affect the values read subsequently;
> only zero may be written in x2APIC mode.) This write clears any
> previously logged errors and updates the ESR with any errors
> detected since the last write to the ESR. This write also rearms the
> APIC error interrupt triggering mechanism.
>
> Update error_interrupt() to remove the first read and follow the Intel
> manual.
>
> Signed-off-by: Javi Merino <javi.merino@cloud.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Not sure whether the plan is to squash your commit and Andrews.
Thanks, Roger.
prev parent reply other threads:[~2024-11-27 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 17:06 [XEN PATCH v1] x86/APIC: Read Error Status Register correctly Javi Merino
2024-11-26 20:07 ` Andrew Cooper
2024-11-27 8:17 ` Jan Beulich
2024-11-26 20:58 ` [PATCH] x86/APIC: Remove workaround Pentium 3AP APIC_ESR erratum Andrew Cooper
2024-11-27 8:20 ` Jan Beulich
2024-11-27 18:01 ` Andrew Cooper
2024-11-28 9:41 ` Jan Beulich
2024-11-28 10:44 ` Andrew Cooper
2024-11-27 8:38 ` Roger Pau Monné
2024-11-27 18:03 ` Andrew Cooper
2024-11-27 10:03 ` Javi Merino
2024-11-27 17:45 ` Andrew Cooper
2024-11-28 9:22 ` Javi Merino
2024-11-27 8:44 ` Roger Pau Monné [this message]
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=Z0bb4t5AIm_NJkFE@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=javi.merino@cloud.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 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.