| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <517041EA.70407@amd.com> Date: Thu, 18 Apr 2013 13:56:42 -0500 From: Suravee Suthikulpanit <suravee.suthikulpanit@....com> To: Joerg Roedel <joro@...tes.org> CC: <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/2 V2] iommu/amd: Add workaround for ERBT1312 On 4/18/2013 1:35 PM, Joerg Roedel wrote: > On Thu, Apr 18, 2013 at 11:59:58AM -0500, Suthikulpanit, Suravee wrote: >> One last concern I have for this patch is the case when we re-enable >> the interrupt, then another interrupt happens while we processing >> the log and set the bit. If the interrupt thread doesn't check this >> right before the thread exits the handler. We could still end up >> leaving the interrupt disabled. > That can't happen, the patch checks whether the bit is really 0 and then > it processes the event/ppr-log entries. If any new entry is queued while > we process the logs another interrupt will be fired and the irq-thread > will run again. So we will not miss any log entry. According to the "kernel/irq/handle.c:irq_wake_thread()", I thought that for the threaded IRQ, if the system getting a new interrupt from the device while the thread is running, it will just return and do nothing. Suravee > Joerg > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists