All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: wangrongwei <rongwei.wang@linux.alibaba.com>
Cc: vkoul@kernel.org, gshan@redhat.com, Anson.Huang@nxp.com,
	geert+renesas@glider.be, catalin.marinas@arm.com,
	masahiroy@kernel.org, linux-kernel@vger.kernel.org,
	krzk@kernel.org, bjorn.andersson@linaro.org, michael@walle.cc,
	olof@lixom.net, shawnguo@kernel.org, vincenzo.frascino@arm.com,
	Will Deacon <will@kernel.org>,
	ardb@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] arm64:msr: Add MSR driver
Date: Tue, 01 Dec 2020 08:12:30 +0000	[thread overview]
Message-ID: <059ed4a8768ff3881005796cb4a10d5e@kernel.org> (raw)
In-Reply-To: <855BA92C-5B22-4F14-965A-B1F72A872B8D@linux.alibaba.com>

On 2020-12-01 03:09, wangrongwei wrote:
> Hi
> We have validate this driver in vm and physical machine, and works 
> fine.

But what does "work fine" mean? None of these system registers are 
supposed
to be accessible from userspace, so please explain *what* you are trying 
to
do with this, other that introducing security holes and general system
instability?

> Actually, we used existing interfaces to realize this driver, likes
> aarch64_insn_read and aarch64_insn_patch_text.

Sure. At that stage, you could also directly expose the linear mapping 
to
userspace and start writing to it, it would probably be a fitting 
addition...

> These existing intefaces had validated a CPU.

If CPU validation is your goal, I suggest this is kept out of tree, as 
the
kernel is hardly a validation tool for the arm64 architecture.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: wangrongwei <rongwei.wang@linux.alibaba.com>
Cc: catalin.marinas@arm.com, Will Deacon <will@kernel.org>,
	bjorn.andersson@linaro.org, shawnguo@kernel.org,
	gshan@redhat.com, geert+renesas@glider.be, Anson.Huang@nxp.com,
	masahiroy@kernel.org, michael@walle.cc, krzk@kernel.org,
	linux-kernel@vger.kernel.org, vkoul@kernel.org, olof@lixom.net,
	vincenzo.frascino@arm.com, ardb@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] arm64:msr: Add MSR driver
Date: Tue, 01 Dec 2020 08:12:30 +0000	[thread overview]
Message-ID: <059ed4a8768ff3881005796cb4a10d5e@kernel.org> (raw)
In-Reply-To: <855BA92C-5B22-4F14-965A-B1F72A872B8D@linux.alibaba.com>

On 2020-12-01 03:09, wangrongwei wrote:
> Hi
> We have validate this driver in vm and physical machine, and works 
> fine.

But what does "work fine" mean? None of these system registers are 
supposed
to be accessible from userspace, so please explain *what* you are trying 
to
do with this, other that introducing security holes and general system
instability?

> Actually, we used existing interfaces to realize this driver, likes
> aarch64_insn_read and aarch64_insn_patch_text.

Sure. At that stage, you could also directly expose the linear mapping 
to
userspace and start writing to it, it would probably be a fitting 
addition...

> These existing intefaces had validated a CPU.

If CPU validation is your goal, I suggest this is kept out of tree, as 
the
kernel is hardly a validation tool for the arm64 architecture.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2020-12-01  8:14 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 17:48 [PATCH 0/3] arm64:msr: Add MSR driver Rongwei Wang
2020-11-30 17:48 ` Rongwei Wang
2020-11-30 17:48 ` [PATCH 1/3] arm64:insn: Export symbols for MSR ARM driver Rongwei Wang
2020-11-30 17:48   ` Rongwei Wang
2020-11-30 17:48 ` [PATCH 2/3] arm64:msr: Introduce " Rongwei Wang
2020-11-30 17:48   ` Rongwei Wang
2020-11-30 23:14   ` kernel test robot
2020-11-30 17:48 ` [PATCH 3/3] arm64:msr: Enable " Rongwei Wang
2020-11-30 17:48   ` Rongwei Wang
2020-11-30 17:57 ` [PATCH 0/3] arm64:msr: Add MSR driver Will Deacon
2020-11-30 17:57   ` Will Deacon
2020-12-01  2:55   ` wangrongwei
2020-12-01  2:55     ` wangrongwei
2020-12-01  5:44   ` wangrongwei
2020-12-01  5:44     ` wangrongwei
2020-11-30 18:05 ` Marc Zyngier
2020-11-30 18:05   ` Marc Zyngier
2020-11-30 18:20   ` Randy Dunlap
2020-11-30 18:20     ` Randy Dunlap
2020-12-01  3:09   ` wangrongwei
2020-12-01  3:09     ` wangrongwei
2020-12-01  8:12     ` Marc Zyngier [this message]
2020-12-01  8:12       ` Marc Zyngier
2020-12-01 14:25       ` wangrongwei
2020-12-01 14:25         ` wangrongwei
2020-12-01 15:37         ` Marc Zyngier
2020-12-01 15:37           ` Marc Zyngier
2020-12-03  5:45           ` Rongwei Wang
2020-12-03  5:45             ` Rongwei Wang
2020-12-03  8:35             ` Marc Zyngier
2020-12-03  8:35               ` Marc Zyngier
2020-12-03 11:25               ` Rongwei Wang
2020-12-03 11:25                 ` Rongwei Wang
2020-12-03 11:45                 ` Marc Zyngier
2020-12-03 11:45                   ` Marc Zyngier
2020-12-03 12:22                   ` Rongwei Wang
2020-12-03 12:22                     ` Rongwei Wang
2020-12-03 11:50                 ` Mark Rutland
2020-12-03 11:50                   ` Mark Rutland
2020-11-30 19:03 ` Borislav Petkov
2020-11-30 19:03   ` Borislav Petkov
2020-12-01  3:44   ` wangrongwei
2020-12-01  3:44     ` wangrongwei
2020-12-01 11:26     ` Borislav Petkov
2020-12-01 11:26       ` Borislav Petkov
2020-12-01 14:33       ` wangrongwei
2020-12-01 14:33         ` wangrongwei
2020-12-01 14:54         ` Borislav Petkov
2020-12-01 14:54           ` Borislav Petkov
2020-12-01 15:17           ` Rongwei Wang
2020-12-01 15:17             ` Rongwei Wang
2020-12-01 15:25             ` Borislav Petkov
2020-12-01 15:25               ` Borislav Petkov
2020-12-03  2:09               ` Rongwei Wang
2020-12-03  2:09                 ` Rongwei Wang
2020-12-01 15:26             ` Ard Biesheuvel
2020-12-01 15:26               ` Ard Biesheuvel

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=059ed4a8768ff3881005796cb4a10d5e@kernel.org \
    --to=maz@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=ardb@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=geert+renesas@glider.be \
    --cc=gshan@redhat.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michael@walle.cc \
    --cc=olof@lixom.net \
    --cc=rongwei.wang@linux.alibaba.com \
    --cc=shawnguo@kernel.org \
    --cc=vincenzo.frascino@arm.com \
    --cc=vkoul@kernel.org \
    --cc=will@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 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.