[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v6] x86: detect CMOS aliasing on ports other than 0x70/0x71
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Thu, 20 Apr 2023 16:31:42 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=8/jlALJv5IVhVxP45HXkIvs+gsd3eb1cG16uDH6fbuc=; b=AAM4KMSsp/TvT9hYbLu0UBPQH3/d1/rS1zEhOQQBXVB2xgfvIVnai1gAVZosr7zDCaULOYciEjLtsiDNOKm7w0xfePMdGZzYlC3JQ+HkHF5O/DD0UNdU63qD3qm6Ry09ckcVyBIgi89+rnL58rVD537fkZhcg1dHik8GFPe4axPUzuTo4EAOj1z68I4f+Jtef/wpb2yPTuhzD2opIGtRnUcgogtuhnLIT6tZC7sUwf0G6rRiOplA+G6oG/esMXW6N2cdeZU/o0JMUac+emR1Ui6YhYj4nQ0uv5mpkRP5z4XjNuU4qaANghcUWyN218AY1+imSEqje7ASxWdqeVAnjg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QFZCBOyWAKCQRAmnXCgJh7g4Gbm/IzzV43EY/AojHazI8Ndg/RloOHvz1o3bzc6wNLxOGo/DD8aLxaGEjFiN95EKWlR/4lH9hzDJccZbpMXyYBf7eJBxj7CDHo/k1i5HbPvMfrH4/Ca2z/jNi511TiuGk9QMDSuZdUuLVohg4OJhEqLlqI34kMlmRul4SmUZaNZoYoC3P2DP0TqS4wIvQhVp06nTG3BFbSGmfunSQPa9TRluBMR8CtTqnpE6of32ooW/JwT9appt898kA3CsLu999gty/jx11P3EnyV8GlrKvTrquXl2bEQvoY/qYQ6vm3pzDdE0FNNoq/m2Fi8eKQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Paul Durrant <paul@xxxxxxx>, Wei Liu <wl@xxxxxxx>
- Delivery-date: Thu, 20 Apr 2023 14:32:18 +0000
- Ironport-data: A9a23:yNvRaKrFbXfnSFWCmJRe2quuxv1eBmIsZBIvgKrLsJaIsI4StFCzt garIBmHP/mOYjDyL95yPIuwoU8A7MXVn9QySApsq3o8Fi8R+ZuZCYyVIHmrMnLJJKUvbq7FA +Y2MYCccZ9uHhcwgj/3b9ANeFEljfngqoLUUbKCYWYpA1c/Ek/NsDo788YhmIlknNOlNA2Ev NL2sqX3NUSsnjV5KQr40YrawP9UlKm06WJwUmAWP6gR5weCzSFNV/rzGInqR5fGatgMdgKFb 76rIIGRpgvx4xorA9W5pbf3GmVirmn6ZFXmZtJ+AsBOszAazsAA+v9T2Mk0MC+7vw6hjdFpo OihgLTrIesf0g8gr8xGO/VQO3kW0aSrY9YrK1Dn2SCY5xWun3cBX5yCpaz5VGEV0r8fPI1Ay RAXAGgOQU2C17+1+arhRblCn854PtG2OpxK7xmMzRmBZRonabbqZvyToPR/hXI3jM0IGuvCb c0EbzYpdA7HfxBEJlYQDtQ5gfusgX78NTZfrTp5p4JuuzSVkFM3jearaYWLEjCJbZw9ckKwv GXJ8n6/GhgHHNee1SCE4jSngeqncSbTAdpMTuzhpqU06LGV7kdCWU0GTVSbnfywilXjccl4e 1Y46BN7+MDe82TuFLERRSaQonSJoxodUNp4CPAh5UeGza+8yxaUAC0IQyBMbPQitdQqXno62 1mRhdTrCDdz9rqPRhq17r6JqRuiNC5TKnUNDQcbSSMV7t+lp5s85i8jVf5mGa+xy9byQDf5x mnTqDBk3upNy8kWy6+84FbLxSq2oYTERRI04QORWX+56gR+Z8iuYInABUXn0Mus5b2xFjGp1 EXoUeDEhAzSJflhTBCwfdg=
- Ironport-hdrordr: A9a23:LeS++6EKv1riyTrVpLqEHseALOsnbusQ8zAXPiBKJCC9vPb5qy nOpoV86faQslwssR4b9uxoVJPvfZqYz+8W3WBzB8bEYOCFghrKEGgK1+KLrwEIWReOk9K1vZ 0KT0EUMqyVMbEVt6fHCAnTKade/DGEmprY+9s3GR1WPHBXg6IL1XYINu6CeHcGPTWvnfACZe ehDswsnUvZRV0nKv6VK1MiROb5q9jChPvdEGI7705O0nj0sduwgoSKaSSl4g==
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Thu, Apr 20, 2023 at 10:31:08AM +0200, Jan Beulich wrote:
> On 19.04.2023 17:55, Roger Pau Monné wrote:
> > On Wed, Apr 19, 2023 at 03:58:10PM +0200, Jan Beulich wrote:
> >> @@ -1342,6 +1349,17 @@ unsigned int rtc_guest_read(unsigned int
> >> * underlying hardware would permit doing so.
> >> */
> >> data = currd->arch.cmos_idx & (0xff >> (port == RTC_PORT(0)));
> >> +
> >> + /*
> >> + * When there's (supposedly) no RTC/CMOS, we don't intercept the
> >> other
> >> + * ports. While reading the index register isn't normally
> >> possible,
> >> + * play safe and return back whatever can be read (just in case a
> >> value
> >> + * written through an alias would be attempted to be read back
> >> here).
> >> + */
> >> + if ( port == RTC_PORT(0) &&
> >> + (acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_CMOS_RTC) &&
> >> + ioports_access_permitted(currd, port, port) )
> >> + data = inb(port) & 0x7f;
> >
> > Do we really need to mask the high bit here? We don't allow setting
> > that bit in the first place.
>
> I think it's more consistent to mask it off, specifically with the code
> visible in context right above the insertion. The doc isn't really clear
> about readability of that bit: On one hand in says R/W for port 0x70 in
> the NMI_EN section, yet otoh in the RTC section it says "Note that port
> 70h is not directly readable. The only way to read this register is
> through Alt Access mode." (I think the NMI_EN section is more trustworthy,
> but still.) Plus if we were to ever make use of the NMI disable, we
> wouldn't want Dom0 see the bit set.
I guess so, at the end Xen itself doesn't use the bit so far. Maybe
at some point we would want to expose the value of the bit to dom0 if
Xen starts using it (most than anything for informative purposes if
NMIs are disabled).
Feel free to fold the diff to the existing patch and keep the RB.
I guess you will also add something to the commit message about the
special handling of the NMI enable bit even when the RTC/CMOS is not
present?
Thanks, Roger.
|