From: Juergen Gross <firstname.lastname@example.org> To: Jan Beulich <email@example.com> Cc: Boris Ostrovsky <firstname.lastname@example.org>, Stefano Stabellini <email@example.com>, Thomas Gleixner <firstname.lastname@example.org>, Ingo Molnar <email@example.com>, Borislav Petkov <firstname.lastname@example.org>, "H. Peter Anvin" <email@example.com>, Peter Zijlstra <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [PATCH 0/3] xen: remove some checks for always present Xen features Date: Thu, 22 Apr 2021 17:49:19 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> [-- Attachment #1.1.1: Type: text/plain, Size: 2038 bytes --] On 22.04.21 17:42, Jan Beulich wrote: > On 22.04.2021 17:28, Juergen Gross wrote: >> On 22.04.21 17:23, Jan Beulich wrote: >>> On 22.04.2021 17:17, Juergen Gross wrote: >>>> On 22.04.21 17:16, Jan Beulich wrote: >>>>> On 22.04.2021 17:10, Juergen Gross wrote: >>>>>> Some features of Xen can be assumed to be always present, so add a >>>>>> central check to verify this being true and remove the other checks. >>>>>> >>>>>> Juergen Gross (3): >>>>>> xen: check required Xen features >>>>>> xen: assume XENFEAT_mmu_pt_update_preserve_ad being set for pv guests >>>>>> xen: assume XENFEAT_gnttab_map_avail_bits being set for pv guests >>>>> >>>>> I wonder whether it's a good idea to infer feature presence from >>>>> version numbers. If (at some point in the past) you had inferred >>>>> gnttab v2 being available by version, this would have been broken >>>>> by its availability becoming controllable by a command line option >>>>> in Xen. >>>> >>>> I'm testing the feature to be really present when booting and issue a >>>> message if it is not there. >>> >>> And how does this help if the feature really isn't there yet other code >>> assumes it is? >> >> Did you look at the features I'm testing? > > I did, yes. > >> Those are really just low >> level additions I can't imagine will ever be removed again. > > I don't expect them to be removed. But I don't think the people having > contributed gnttab v2 expected any such for it, either. There is a major difference here. gnttab v2 was replacing an existing functionality by a more scalable, but more complex solution. The features I'm assuming to be present are basically repairing issues which have been present due to omissions in the initial implementation. Especially the XENFEAT_gnttab_map_avail_bits causes a racy workaround in the kernel when not present. The race is only avoided in case the user code is well-behaved. It is dom0 user code, yes, but nevertheless such issues are never nice. Juergen [-- Attachment #1.1.2: OpenPGP_0xB0DE9DD628BF132F.asc --] [-- Type: application/pgp-keys, Size: 3135 bytes --] [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-04-22 15:49 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-22 15:10 Juergen Gross 2021-04-22 15:10 ` [PATCH 1/3] xen: check required " Juergen Gross 2021-04-22 15:26 ` Stefano Stabellini 2021-04-22 15:32 ` Juergen Gross 2021-05-10 12:11 ` Boris Ostrovsky 2021-05-10 13:21 ` Juergen Gross 2021-04-22 15:10 ` [PATCH 2/3] xen: assume XENFEAT_mmu_pt_update_preserve_ad being set for pv guests Juergen Gross 2021-04-22 15:10 ` [PATCH 3/3] xen: assume XENFEAT_gnttab_map_avail_bits " Juergen Gross 2021-04-22 15:16 ` [PATCH 0/3] xen: remove some checks for always present Xen features Jan Beulich 2021-04-22 15:17 ` Juergen Gross 2021-04-22 15:23 ` Jan Beulich 2021-04-22 15:28 ` Juergen Gross 2021-04-22 15:42 ` Jan Beulich 2021-04-22 15:49 ` Juergen Gross [this message] 2021-04-22 15:51 ` Andrew Cooper 2021-05-10 7:34 ` Juergen Gross 2021-05-10 11:31 ` Peter Zijlstra
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/3] xen: remove some checks for always present Xen features' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).