[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 8/8] xen/evtchn: use READ/WRITE_ONCE() for accessing ring indices
- To: Juergen Gross <jgross@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- From: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
- Date: Sat, 20 Feb 2021 15:35:53 -0500
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oracle.com; dmarc=pass action=none header.from=oracle.com; dkim=pass header.d=oracle.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Ttjp2TZJU+U2UIOOLpcWd1iIjWpC5sFOUFSHTnkE3mU=; b=XJPWrLwzVhhCjt6dB1iFqZXSDq8/UyvQPPvWGP1q7jMg4G/Y08GQACLs6CCcg7RWCGTU4KCEwJSl25TFQs5j6OqpIS2E4SzkEhEa9wG5tmCkD59ntyEG9LSdeI3tx84+sgtjDNOBs7zDo3YsJ8NypYjD4nCMCQ1C34GGdqsAl5vVowVBa+czHpwjBKcudyEqL99bugwqtu7scq1pnbfn64cKYOgOC561fj+wSkWOAP8l1ZXSkIoBLrjqy8daP2g2glFLx/3s2RmfMi2JyonygmyAAv1C95x7H8OPOCfQRO3Ndj4VJO8q3+DozDUQCiS6c6L4LIhqbeQ4lugsMqG77g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ENV4ehp03eIj0SSnQAs96rP91js2iu9jrzg41p7haHcRXOJiQIXF47u9HVUUPe8ySYf+XPhyCWVeXulOFZZRLKYjBGYRil+1Rt6NoSOCmMJhdQyIh++dr/VW1ZxBt31n/d0AuHgBL14XGNurj0cBNTpOdSY3vc36u54vZ7fmwm1DaoSizSA2BSoKFo/XpGt8SQqF39Wt2yi2WE1ayV3ZF1t8It8EzqPLkfcqhgcTCiPOMZB1x4isxAgiR2Bj2V/I+gmpjepeq/CLz8umgm6iyr78LM2GcAJ0n2jxpzMF8qH+Tf553q0KaA7//vC99XR3Y+O87Gkak9C9E6Lv7nv+RA==
- Authentication-results: kernel.org; dkim=none (message not signed) header.d=none;kernel.org; dmarc=none action=none header.from=oracle.com;
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>
- Delivery-date: Sat, 20 Feb 2021 20:36:11 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 2/19/21 10:40 AM, Juergen Gross wrote:
> For avoiding read- and write-tearing by the compiler use READ_ONCE()
> and WRITE_ONCE() for accessing the ring indices in evtchn.c.
>
> Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
|
