From: Andrew Cooper <andrew.cooper3@citrix.com>
To: dmkhn@proton.me, xen-devel@lists.xenproject.org
Cc: jbeulich@suse.com, roger.pau@citrix.com,
nicola.vetrini@bugseng.com, consulting@bugseng.com,
dmukhin@ford.com, Stefano Stabellini <sstabellini@kernel.org>
Subject: [PING MISRA] Re: [PATCH v5 2/2] x86/vmx: remove __vmread()
Date: Fri, 16 May 2025 13:45:06 +0100 [thread overview]
Message-ID: <85f778d1-7fb5-47da-9153-35333e486d24@citrix.com> (raw)
In-Reply-To: <20250513052809.3947164-3-dmukhin@ford.com>
Hello,
This is adjusting some MISRA configuration. I'm reasonably sure the
change is fine as we're simply removing the referenced helper, but can
we get a second opinion from anyone who knows what
function-macro-properties.json is supposed to be doing?
Thanks,
~Andrew
On 13/05/2025 6:28 am, dmkhn@proton.me wrote:
> From: Denis Mukhin <dmukhin@ford.com>
>
> Remove __vmread() and adjust ECLAIR configuration to account for the change.
>
> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> ---
> docs/misra/function-macro-properties.json | 9 ---------
> xen/arch/x86/include/asm/hvm/vmx/vmx.h | 5 -----
> 2 files changed, 14 deletions(-)
>
> diff --git a/docs/misra/function-macro-properties.json b/docs/misra/function-macro-properties.json
> index 74058297b5..59ba63626e 100644
> --- a/docs/misra/function-macro-properties.json
> +++ b/docs/misra/function-macro-properties.json
> @@ -152,15 +152,6 @@
> "taken": ""
> }
> },
> - {
> - "type": "function",
> - "value": "^__vmread.*$",
> - "properties":{
> - "pointee_write": "2=always",
> - "pointee_read": "2=never",
> - "taken": ""
> - }
> - },
> {
> "type": "function",
> "value": "^hvm_pci_decode_addr.*$",
> diff --git a/xen/arch/x86/include/asm/hvm/vmx/vmx.h b/xen/arch/x86/include/asm/hvm/vmx/vmx.h
> index d85b52b9d5..299e2eff6b 100644
> --- a/xen/arch/x86/include/asm/hvm/vmx/vmx.h
> +++ b/xen/arch/x86/include/asm/hvm/vmx/vmx.h
> @@ -336,11 +336,6 @@ static always_inline unsigned long vmread(unsigned long field)
> return value;
> }
>
> -static always_inline void __vmread(unsigned long field, unsigned long *value)
> -{
> - *value = vmread(field);
> -}
> -
> static always_inline void __vmwrite(unsigned long field, unsigned long value)
> {
> asm goto ( "vmwrite %[value], %[field]\n\t"
next prev parent reply other threads:[~2025-05-16 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 5:28 [PATCH v5 0/2] x86/vmx: __vmread() cleanup dmkhn
2025-05-13 5:28 ` [PATCH v5 1/2] x86/vmx: replace __vmread() with vmread() dmkhn
2025-05-16 12:42 ` Andrew Cooper
2025-05-16 17:41 ` dmkhn
2025-05-13 5:28 ` [PATCH v5 2/2] x86/vmx: remove __vmread() dmkhn
2025-05-16 12:45 ` Andrew Cooper [this message]
2025-05-16 12:53 ` [PING MISRA] " Nicola Vetrini
2025-05-16 12:54 ` Andrew Cooper
2025-05-16 18:07 ` dmkhn
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=85f778d1-7fb5-47da-9153-35333e486d24@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.