From: Borislav Petkov <firstname.lastname@example.org> To: "Bae, Chang Seok" <email@example.com> Cc: Andy Lutomirski <firstname.lastname@example.org>, Thomas Gleixner <email@example.com>, "firstname.lastname@example.org" <email@example.com>, "firstname.lastname@example.org" <email@example.com>, "Brown, Len" <firstname.lastname@example.org>, "Hansen, Dave" <email@example.com>, "Liu, Jing2" <firstname.lastname@example.org>, "Shankar, Ravi V" <email@example.com>, "firstname.lastname@example.org" <email@example.com>, "firstname.lastname@example.org" <email@example.com> Subject: Re: [PATCH v3 06/21] x86/fpu/xstate: Calculate and remember dynamic xstate buffer sizes Date: Wed, 27 Jan 2021 10:38:10 +0100 [thread overview] Message-ID: <20210127093810.GA8115@zn.tnic> (raw) In-Reply-To: <6811FA0A-21A6-4519-82B8-C128C30127E0@intel.com> On Wed, Jan 27, 2021 at 01:23:35AM +0000, Bae, Chang Seok wrote: > How about ‘embedded’?, > “The xstate buffer is currently embedded into struct fpu with static size." Better. > Okay. I will prepare a separate cleanup patch that can be applied at the end > of the series. Will post the change in this thread at first. No, this is not how this works. Imagine you pile up a patch at the end for each review feedback you've gotten. No, this will be an insane churn and an unreviewable mess. What you do is you rework your patches like everyone else. Also, thinking about this more, I'm wondering if all those xstate-related attributes shouldn't be part of struct fpu instead of being scattered around like that. That thing - struct fpu * - gets passed in everywhere anyway so all that min_size, max_size, ->xstate_ptr and whatever, looks like it wants to be part of struct fpu. Then maybe you won't need the accessors... > One of my drafts had some internal helper to be called in there. No reason > prior to applying the get_xstate_buffer_attr() helper. But with it, better to > move this out of this header file I think. See above. > > >> @@ -627,13 +627,18 @@ static void check_xstate_against_struct(int nr) > >> */ > > > > <-- There's a comment over this function that might need adjustment. > > Do you mean an empty line? (Just want to clarify.) No, I mean this comment: * Dynamic XSAVE features allocate their own buffers and are not * covered by these checks. Only the size of the buffer for task->fpu * is checked here. That probably needs adjusting as you do set min and max size here now for the dynamic buffer. > Agreed. I will prepare a patch. At least will post the diff here. You can send it separately from this patchset, ontop of current tip/master, so that I can take it now. > How about: > “Ensure the size fits in the statically-allocated buffer:" Yep. > No excuse, just pointing out the upstream code has “we” there . Yeah, I know. :-\ But considering how many parties develop the kernel now, "we" becomes really ambiguous. Thx. -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2021-01-27 9:41 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> 2020-12-23 15:56 ` [PATCH v3 01/21] x86/fpu/xstate: Modify initialization helper to handle both static and dynamic buffers Chang S. Bae 2021-01-15 12:40 ` Borislav Petkov 2020-12-23 15:56 ` [PATCH v3 03/21] x86/fpu/xstate: Modify address finders " Chang S. Bae 2021-01-15 13:06 ` Borislav Petkov 2020-12-23 15:57 ` [PATCH v3 04/21] x86/fpu/xstate: Modify context switch helpers " Chang S. Bae 2021-01-15 13:18 ` Borislav Petkov 2021-01-19 18:49 ` Bae, Chang Seok 2020-12-23 15:57 ` [PATCH v3 06/21] x86/fpu/xstate: Calculate and remember dynamic xstate buffer sizes Chang S. Bae 2021-01-22 11:44 ` Borislav Petkov 2021-01-27 1:23 ` Bae, Chang Seok 2021-01-27 9:38 ` Borislav Petkov [this message] 2021-02-03 2:54 ` Bae, Chang Seok 2020-12-23 15:57 ` [PATCH v3 10/21] x86/fpu/xstate: Update xstate save function to support dynamic xstate Chang S. Bae 2021-01-07 8:41 ` Liu, Jing2 2021-01-07 18:40 ` Bae, Chang Seok 2021-01-12 2:52 ` Liu, Jing2 2021-01-15 4:59 ` Bae, Chang Seok 2021-01-15 5:45 ` Liu, Jing2 2021-02-08 12:33 ` Borislav Petkov 2021-02-09 15:48 ` Bae, Chang Seok
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 \ --in-reply-to=20210127093810.GA8115@zn.tnic \ --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 v3 06/21] x86/fpu/xstate: Calculate and remember dynamic xstate buffer sizes' \ /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).