Ping: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-08-24 Thread Jan Beulich
On 24.07.2020 16:19, Jan Beulich wrote: > On 24.07.2020 14:11, Andrew Cooper wrote: >> On 17/07/2020 14:10, Jan Beulich wrote: >>> Since we intercept RTC/CMOS port accesses, let's do so consistently in >>> all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid >>> the risk of

Re: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-24 Thread Jan Beulich
On 24.07.2020 14:11, Andrew Cooper wrote: > On 17/07/2020 14:10, Jan Beulich wrote: >> Since we intercept RTC/CMOS port accesses, let's do so consistently in >> all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid >> the risk of unintended impact on Dom0 code actually doing so

Re: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-24 Thread Andrew Cooper
On 17/07/2020 14:10, Jan Beulich wrote: > Since we intercept RTC/CMOS port accesses, let's do so consistently in > all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid > the risk of unintended impact on Dom0 code actually doing so (despite > the belief that none ought to exist),

Re: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-20 Thread Roger Pau Monné
On Mon, Jul 20, 2020 at 01:58:40PM +0200, Jan Beulich wrote: > On 20.07.2020 12:52, Roger Pau Monné wrote: > > On Fri, Jul 17, 2020 at 03:10:43PM +0200, Jan Beulich wrote: > >> Since we intercept RTC/CMOS port accesses, let's do so consistently in > >> all cases, i.e. also for e.g. a dword access

Re: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-20 Thread Jan Beulich
On 20.07.2020 12:52, Roger Pau Monné wrote: > On Fri, Jul 17, 2020 at 03:10:43PM +0200, Jan Beulich wrote: >> Since we intercept RTC/CMOS port accesses, let's do so consistently in >> all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid >> the risk of unintended impact on Dom0

Re: [PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-20 Thread Roger Pau Monné
On Fri, Jul 17, 2020 at 03:10:43PM +0200, Jan Beulich wrote: > Since we intercept RTC/CMOS port accesses, let's do so consistently in > all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid > the risk of unintended impact on Dom0 code actually doing so (despite > the belief that

[PATCH] x86: guard against port I/O overlapping the RTC/CMOS range

2020-07-17 Thread Jan Beulich
Since we intercept RTC/CMOS port accesses, let's do so consistently in all cases, i.e. also for e.g. a dword access to [006E,0071]. To avoid the risk of unintended impact on Dom0 code actually doing so (despite the belief that none ought to exist), also extend guest_io_{read,write}() to decompose