From: Borislav Petkov <bp@alien8.de>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: x86-ml <x86@kernel.org>, Joerg Roedel <jroedel@suse.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Have insn decoder functions return success/failure
Date: Wed, 21 Oct 2020 11:27:50 +0200 [thread overview]
Message-ID: <20201021092750.GA4050@zn.tnic> (raw)
In-Reply-To: <20201021095013.d82637f84af564ae4363189d@kernel.org>
On Wed, Oct 21, 2020 at 09:50:13AM +0900, Masami Hiramatsu wrote:
> Agreed. So I'm OK for returning the result of "decoding".
> But we also need to note that the returning success doesn't
> mean the instruction is valid. That needs another validator.
>
...
>
> Yes, so let's add the return value (with a note, so that someone
> does not try to use it for validation).
Ok, I'm unclear on that "validation" you talk about. What exactly do
you mean? Can you give an example of how one would determine whether an
instruction is valid? And valid how?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-21 9:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 12:02 [RFC] Have insn decoder functions return success/failure Borislav Petkov
2020-10-20 14:27 ` Masami Hiramatsu
2020-10-20 14:37 ` Borislav Petkov
2020-10-21 0:50 ` Masami Hiramatsu
2020-10-21 9:27 ` Borislav Petkov [this message]
2020-10-21 14:26 ` Masami Hiramatsu
2020-10-21 16:45 ` Borislav Petkov
2020-10-22 7:31 ` Masami Hiramatsu
2020-10-22 9:30 ` Borislav Petkov
2020-10-22 13:21 ` Masami Hiramatsu
2020-10-22 17:58 ` Andy Lutomirski
2020-10-23 9:20 ` Borislav Petkov
2020-10-23 9:28 ` Masami Hiramatsu
2020-10-23 9:32 ` Borislav Petkov
2020-10-23 10:47 ` Masami Hiramatsu
2020-10-23 23:27 ` Borislav Petkov
2020-10-24 0:12 ` Andy Lutomirski
2020-10-24 7:21 ` Masami Hiramatsu
2020-10-24 8:23 ` Borislav Petkov
2020-10-24 16:10 ` Andy Lutomirski
2020-10-27 13:42 ` Borislav Petkov
2020-10-28 11:36 ` Masami Hiramatsu
2020-10-24 7:13 ` Masami Hiramatsu
2020-10-24 8:24 ` Borislav Petkov
2020-10-29 12:42 ` Borislav Petkov
2020-10-30 1:24 ` Masami Hiramatsu
2020-10-30 13:07 ` Borislav Petkov
2020-10-23 9:17 ` Borislav Petkov
2020-10-22 8:04 ` 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 \
--in-reply-to=20201021092750.GA4050@zn.tnic \
--to=bp@alien8.de \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox