> -----Original Message-----
> From: Andrew Cooper <[email protected]>
> Sent: 30 July 2020 18:34
> To: [email protected]; 'Xen-devel' <[email protected]>
> Cc: 'Jan Beulich' <[email protected]>; 'Wei Liu' <[email protected]>; 'Roger Pau 
> Monné'
> <[email protected]>; 'Stefano Stabellini' <[email protected]>; 
> 'Julien Grall'
> <[email protected]>; 'Volodymyr Babchuk' <[email protected]>; 'Michał 
> Leszczyński'
> <[email protected]>; 'Hubert Jasudowicz' <[email protected]>
> Subject: Re: [PATCH 1/5] xen/memory: Introduce CONFIG_ARCH_ACQUIRE_RESOURCE
> 
> On 30/07/2020 09:02, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Andrew Cooper <[email protected]>
> >> Sent: 28 July 2020 12:37
> >> To: Xen-devel <[email protected]>
> >> Cc: Andrew Cooper <[email protected]>; Jan Beulich 
> >> <[email protected]>; Wei Liu
> <[email protected]>;
> >> Roger Pau Monné <[email protected]>; Stefano Stabellini 
> >> <[email protected]>; Julien Grall
> >> <[email protected]>; Volodymyr Babchuk <[email protected]>; Paul 
> >> Durrant <[email protected]>;
> Michał
> >> Leszczyński <[email protected]>; Hubert Jasudowicz 
> >> <[email protected]>
> >> Subject: [PATCH 1/5] xen/memory: Introduce CONFIG_ARCH_ACQUIRE_RESOURCE
> >>
> >> New architectures shouldn't be forced to implement no-op stubs for unused
> >> functionality.
> >>
> >> Introduce CONFIG_ARCH_ACQUIRE_RESOURCE which can be opted in to, and 
> >> provide
> >> compatibility logic in xen/mm.h
> >>
> >> No functional change.
> > Code-wise, it looks fine, so...
> >
> > Reviewed-by: Paul Durrant <[email protected]>
> 
> Thanks,
> 
> >
> > ...but ...
> >
> >> Signed-off-by: Andrew Cooper <[email protected]>
> >> ---
> >> CC: Jan Beulich <[email protected]>
> >> CC: Wei Liu <[email protected]>
> >> CC: Roger Pau Monné <[email protected]>
> >> CC: Stefano Stabellini <[email protected]>
> >> CC: Julien Grall <[email protected]>
> >> CC: Volodymyr Babchuk <[email protected]>
> >> CC: Paul Durrant <[email protected]>
> >> CC: Michał Leszczyński <[email protected]>
> >> CC: Hubert Jasudowicz <[email protected]>
> >> ---
> >>  xen/arch/x86/Kconfig     | 1 +
> >>  xen/common/Kconfig       | 3 +++
> >>  xen/include/asm-arm/mm.h | 8 --------
> >>  xen/include/xen/mm.h     | 9 +++++++++
> >>  4 files changed, 13 insertions(+), 8 deletions(-)
> >>
> >> diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
> >> index a636a4bb1e..e7644a0a9d 100644
> >> --- a/xen/arch/x86/Kconfig
> >> +++ b/xen/arch/x86/Kconfig
> >> @@ -6,6 +6,7 @@ config X86
> >>    select ACPI
> >>    select ACPI_LEGACY_TABLES_LOOKUP
> >>    select ARCH_SUPPORTS_INT128
> >> +  select ARCH_ACQUIRE_RESOURCE
> > ... I do wonder whether 'HAS_ACQUIRE_RESOURCE' is a better and more 
> > descriptive name.
> 
> We don't have a coherent policy for how to categorise these things.  I
> can change the name if you insist, but I'm not sure it makes a useful
> difference.
> 

Ok, it's fine. My R-b stands.

  Paul

> ~Andrew


Reply via email to