Hi Andrey
On Tue, 26 Jan 2021 at 07:50, Andrey Konovalov
wrote:
>
> This control is needed for imx219 driver, as the link frequency
> is independent from the pixel rate in this case, and can't be
> calculated from the pixel rate.
>
> Signed-off-by: Andrey Konovalov
> ---
> drivers/media/i2c/imx
Hi Russell,
> Those who cause breakage really should be the ones to look at patches
> that fix their breakage.
Does it mean you want an explicit ack from Thomas or that it should go
via his tree?
> The way patches get applied is if they end up in my patch system... if
> they don't make it there,
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hfi1/verbs.c:741: warning: Function parameter or member
'qp' not described in 'update_tx_opstats'
drivers/infiniband/hw/hfi1/verbs.c:1160: warning: Function parameter or member
'pkey' not described in 'egress_pkey_check'
d
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hfi1/user_exp_rcv.c:174: warning: Function parameter or
member 'fd' not described in 'unpin_rcv_pages'
drivers/infiniband/hw/hfi1/user_exp_rcv.c:174: warning: Function parameter or
member 'tidbuf' not described in 'unpin_rc
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hfi1/pio_copy.c:73: warning: Function parameter or
member 'dd' not described in 'pio_copy'
Cc: Mike Marciniszyn
Cc: Dennis Dalessandro
Cc: Doug Ledford
Cc: Jason Gunthorpe
Cc: linux-r...@vger.kernel.org
Signed-off-by: Le
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hfi1/intr.c:99: warning: Function parameter or member
'msg' not described in 'format_hwmsg'
drivers/infiniband/hw/hfi1/intr.c:99: warning: Function parameter or member
'msgl' not described in 'format_hwmsg'
drivers/infinib
Fixes the following W=1 kernel build warning(s):
drivers/clk/zynqmp/divider.c:46: warning: Function parameter or member
'max_div' not described in 'zynqmp_clk_divider'
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Michal Simek
Cc: Rajan Vaja
Cc: linux-...@vger.kernel.org
Cc: linux-arm-ker...@l
Fixes the following W=1 kernel build warning(s):
drivers/clk/imx/clk-imx6sl.c:156:6: warning: no previous prototype for
‘imx6sl_set_wait_clk’ [-Wmissing-prototypes]
Cc: Russell King
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Cc: Ahmad F
Fixes the following W=1 kernel build warning(s):
drivers/clk/sunxi/clk-sun6i-ar100.c:26: warning: Function parameter or member
'req' not described in 'sun6i_get_ar100_factors'
Cc: "Emilio López"
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Cc: Jernej Skrabec
C
Fixes the following W=1 kernel build warning(s):
drivers/clk/renesas/renesas-cpg-mssr.c:168: warning: Function parameter or
member 'smstpcr_saved' not described in 'cpg_mssr_priv'
Cc: Geert Uytterhoeven
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Philipp Zabel
Cc: linux-renesas-...@vger.kern
Fixes the following W=1 kernel build warning(s):
drivers/clk/clk-npcm7xx.c:438:43: warning: ‘npcm7xx_gates’ defined but not
used [-Wunused-const-variable=]
drivers/clk/clk-npcm7xx.c:365:48: warning: ‘npcm7xx_divs_fx’ defined but not
used [-Wunused-const-variable=]
Cc: Avi Fishman
Cc: Tomer M
Fixes the following W=1 kernel build warning(s):
drivers/clk/spear/spear1310_clock.c:385:13: warning: no previous prototype for
‘spear1310_clk_init’ [-Wmissing-prototypes]
drivers/clk/spear/spear1340_clock.c:442:13: warning: no previous prototype for
‘spear1340_clk_init’ [-Wmissing-prototypes]
The device iommu probe/attach might have failed leaving dev->iommu
to NULL and device drivers may still invoke these functions resulting
a crash in iommu vendor driver code. Hence make sure we check that.
Signed-off-by: Shameer Kolothum
---
drivers/iommu/iommu.c | 8
1 file changed, 4 i
Fixes the following W=1 kernel build warning(s):
drivers/clk/qcom/mmcc-msm8974.c:85:27: warning: ‘mmcc_xo_mmpll0_1_2_gpll0’
defined but not used [-Wunused-const-variable=]
drivers/clk/qcom/mmcc-msm8974.c:77:32: warning: ‘mmcc_xo_mmpll0_1_2_gpll0_map’
defined but not used [-Wunused-const-variab
Fixes the following W=1 kernel build warning(s):
drivers/clk/clk-xgene.c:229: warning: Function parameter or member 'mask' not
described in 'xgene_clk_pmd'
drivers/clk/clk-xgene.c:229: warning: Function parameter or member 'flags' not
described in 'xgene_clk_pmd'
Cc: Michael Turquette
Cc: St
Fixes the following W=1 kernel build warning(s):
drivers/clk/ti/dpll44xx.c:114: warning: Function parameter or member 'hw' not
described in 'omap4_dpll_regm4xen_recalc'
drivers/clk/ti/dpll44xx.c:114: warning: Function parameter or member
'parent_rate' not described in 'omap4_dpll_regm4xen_reca
Fixes the following W=1 kernel build warning(s):
drivers/clk/tegra/cvb.c:106: warning: Function parameter or member 'align' not
described in 'tegra_cvb_add_opp_table'
Cc: Peter De Schrijver
Cc: Prashant Gaikwad
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Thierry Reding
Cc: Jonathan Hunter
Fixes the following W=1 kernel build warning(s):
drivers/clk/qcom/clk-rpm.c:453:29: warning: ‘clk_rpm_branch_ops’ defined but
not used [-Wunused-const-variable=]
Cc: Andy Gross
Cc: Bjorn Andersson
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: linux-arm-...@vger.kernel.org
Cc: linux-...@vger.ke
Fixes the following W=1 kernel build warning(s):
drivers/clk/tegra/clk-tegra30.c: In function ‘tegra30_enable_cpu_clock’:
drivers/clk/tegra/clk-tegra30.c:1107:15: warning: variable ‘reg’ set but not
used [-Wunused-but-set-variable]
Cc: Peter De Schrijver
Cc: Prashant Gaikwad
Cc: Michael Turq
Fixes the following W=1 kernel build warning(s):
drivers/clk/sunxi/clk-usb.c:22: warning: cannot understand function prototype:
'struct usb_reset_data '
Cc: "Emilio López"
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Cc: Jernej Skrabec
Cc: Philipp Zabel
Cc: l
Headers must describe their parameters.
Fixes the following W=1 kernel build warning(s):
drivers/clk/sunxi/clk-sun9i-core.c:27: warning: Function parameter or member
'req' not described in 'sun9i_a80_get_pll4_factors'
drivers/clk/sunxi/clk-sun9i-core.c:100: warning: Function parameter or membe
On 23/01/2021 05:44, Stephen Boyd wrote:
Use the more modern API to get the match data out of the of match table.
This saves some code, lines, and nicely avoids referencing the match
table when it is undefined with configurations where CONFIG_OF=n.
Signed-off-by: Stephen Boyd
Cc: Arnd Bergma
Fixes the following W=1 kernel build warning(s):
drivers/clk/ti/dpll3xxx.c:414: warning: Function parameter or member 'hw' not
described in 'omap3_dpll_recalc'
drivers/clk/ti/dpll3xxx.c:414: warning: Function parameter or member
'parent_rate' not described in 'omap3_dpll_recalc'
drivers/clk/t
From: Yang Yang
No invoker users the return value of audit_filter_syscall().
So make it return void.
Signed-off-by: Yang Yang
---
kernel/auditsc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/auditsc.c b/kernel/auditsc.c
index ce8c9e2279ba..c8e16b9c0f21 10
Add simple IRQ or GPIO base pulse counter. This device is used to measure
rotation speed of some agricultural devices, so no high frequency on the
counter pin is expected.
The maximal measurement frequency depends on the CPU and system load. On
the idle iMX6S I was able to measure up to 20kHz with
changes v4:
- use IRQ_NOAUTOEN to not enable IRQ by default
- rename gpio_ from name pattern and make this driver work any IRQ
source.
changes v3:
- convert counter to atomic_t
changes v2:
- add commas
- avoid possible unhandled interrupts in the enable path
- do not use of_ specific gpio funct
On 21-01-26 12:51:05, Sascha Hauer wrote:
> On Tue, Jan 26, 2021 at 01:21:36PM +0200, Abel Vesa wrote:
> > Some clocks are already enabled in HW even before the kernel
> > starts to boot. So, in order to make sure that these clocks do not
> > get disabled when clk_disable_unused call is done or whe
Add binding for the pulse counter node
Signed-off-by: Oleksij Rempel
---
.../bindings/counter/pulse-counter.yaml | 52 +++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/counter/pulse-counter.yaml
diff --git a/Documentation/devicetre
Fixes the following W=1 kernel build warning(s):
drivers/clk/ti/clkt_dpll.c:284: warning: Function parameter or member 'hw' not
described in 'omap2_dpll_round_rate'
drivers/clk/ti/clkt_dpll.c:284: warning: Function parameter or member
'parent_rate' not described in 'omap2_dpll_round_rate'
dri
This function write protects all PTEs between the ffs and fls of mask.
There may has unset bit between this range. It works well under pure
software dirty log, as software dirty log is not working during this
process.
But it will unexpectly clear dirty status of PTE when hardware dirty
log is enab
We do not enable hardware dirty at start (do not add DBM bit). When
an arbitrary PT occurs fault, we execute soft tracking for this PT
and enable hardware tracking for its nearby PTs (Add DBM bit for
nearby 64PTs). Then when sync dirty log, we have known all PTs with
hardware dirty enabled, so we d
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
tags/regulator-fix-v5.11-rc5
for you to fetch changes up to
On Tue, Jan 26, 2021 at 2:21 AM Greg KH wrote:
>
> On Mon, Jan 25, 2021 at 04:07:57PM -0600, Josh Poimboeuf wrote:
> > On Tue, Jan 26, 2021 at 06:44:35AM +0900, Masahiro Yamada wrote:
> > > > > If people use a different compiler, they must be
> > > > > prepared for any possible problem.
> > > > >
This adds set_dbm, clear_dbm and sync_dirty interfaces in pgtable
layer. (1) set_dbm: Set DBM bit for last level PTE of a specified
range. TLBI is completed. (2) clear_dbm: Clear DBM bit for last
level PTE of a specified range. TLBI is not acted. (3) sync_dirty:
Scan last level PTE of a specific ra
In order to change PTEs of some specific levels, the level_apply
parameter can be used as a level mask.
This has no fuctional change for current code.
Signed-off-by: Keqian Zhu
---
arch/arm64/kvm/hyp/pgtable.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --gi
The intention:
On arm64 platform, we tracking dirty log of vCPU through guest memory abort.
KVM occupys some vCPU time of guest to change stage2 mapping and mark dirty.
This leads to heavy side effect on VM, especially when multi vCPU race and
some of them block on kvm mmu_lock.
DBM is a HW auxil
On Tue, 26 Jan 2021 11:17:45 +0300
Dan Carpenter wrote:
> On Mon, Jan 25, 2021 at 04:44:12PM +0800, Carlis wrote:
> > From: "carlis.zhang_cp"
>
> I was really expecting that you would fix this and Signed-off-by as
> well.
>
> regards,
> dan carpenter
>
I have fix this in patch v3
> regards,
We are about to add HW_DBM support for stage2 dirty log, so software
updating PTE may race with the MMU trying to set the access flag or
dirty state.
Use atomic oparations to avoid reverting these bits set by MMU.
Signed-off-by: Keqian Zhu
---
arch/arm64/kvm/hyp/pgtable.c | 41 +
On Tue, Jan 26, 2021 at 08:33:37AM +0100, Mike Looijmans wrote:
> The mdio_bus reset code first de-asserted the reset by allocating with
> GPIOD_OUT_LOW, then asserted and de-asserted again. In other words, if
> the reset signal defaulted to asserted, there'd be a short "spike"
> before the reset.
Though we already has a cpu capability named ARM64_HW_DBM, it's a
LOCAL_CPU cap and conditionally compiled by CONFIG_ARM64_HW_AFDBM.
This reports the system wide support of HW_DBM.
Signed-off-by: Keqian Zhu
---
arch/arm64/include/asm/cpufeature.h | 12
1 file changed, 12 insertions
Hi Moritz,
Thanks for your reviews!
On 1/25/21 11:01 PM, Moritz Fischer wrote:
Hi Richard,
On Mon, Jan 25, 2021 at 02:56:24PM -0600, richard.g...@linux.intel.com wrote:
From: Richard Gong
Extend Intel service layer driver to get the firmware version running at
FPGA device. Therefore FPGA ma
This patch adds spi host nodes for MT6779 SOC
Hi Moritz,
On 1/25/21 11:04 PM, Moritz Fischer wrote:
On Mon, Jan 25, 2021 at 02:56:25PM -0600, richard.g...@linux.intel.com wrote:
From: Richard Gong
Add FPGA_MGR_BITSTREM_AUTHENTICATION flag for FPGA bitstream
authentication, which makes sure a signed bitstream has valid signatures.
Exce
Hi Amélie,
On 1/14/21 2:15 PM, Amelie Delaunay wrote:
This series updates usbphyc parent and child nodes to follow latest DT
bindings.
---
Changes in v2:
- squash all DT board patches in one patch
- update also non-ST DT
Amelie Delaunay (3):
ARM: dts: stm32: add usbphyc vdda1v1 and vdda1v8
This adds set_dbm, clear_dbm and sync_dirty interfaces in mmu layer.
They simply wrap those interfaces of pgtable layer, adding reschedule
semantics.
Signed-off-by: Keqian Zhu
---
arch/arm64/include/asm/kvm_mmu.h | 7 +++
arch/arm64/kvm/mmu.c | 30 ++
ATTENTION;
IMPORTANT INVESTMENT INFORMATION
We have a good investment program going on now.
We have $95m USD for Investment in your Country. We use this opportunity to
invest you to join the investment program and you will never regret it.
Please kindly invest with us and you will be receiving mon
Fixes the following W=1 kernel build warning(s):
drivers/clk/zynq/pll.c:187: warning: Function parameter or member 'name' not
described in 'clk_register_zynq_pll'
drivers/clk/zynq/pll.c:187: warning: Function parameter or member 'parent' not
described in 'clk_register_zynq_pll'
drivers/clk/zy
From: Guillaume Nault
commit 2e5a6266fbb11ae93c468dfecab169aca9c27b43 upstream.
RT_TOS() only masks one of the two ECN bits. Therefore rpfilter_mt()
treats Not-ECT or ECT(1) packets in a different way than those with
ECT(0) or CE.
Reproducer:
Create two netns, connected with a veth:
$ ip n
On Tue, 26 Jan 2021 10:54:41 +0300
Dan Carpenter wrote:
> On Sun, Jan 24, 2021 at 11:35:37PM +0800, Carlis wrote:
> > +static irqreturn_t spi_panel_te_handler(int irq, void *data)
> > +{
> > + complete(&spi_panel_te);
> > + return IRQ_HANDLED;
> > +}
> > +
> > +static void enable_spi_panel_te
The ATC260x family of PMICs integrates Audio Codec, Power management,
Clock generation and GPIO controller blocks. There are currently 3
variants: ATC2603A, ATC2603C and ATC2609A.
This is re-spin of the v1 patch series submitted some time ago by
Mani, who provided the MFD and regulator drivers for
Add initial support for the Actions Semi ATC260x PMICs which integrates
Audio Codec, Power management, Clock generation and GPIO controller
blocks.
For the moment this driver only supports Regulator, Poweroff and Onkey
functionalities for the ATC2603C and ATC2609A chip variants.
Since the PMICs c
From: Manivannan Sadhasivam
Add MAINTAINERS entry for ATC260x PMIC.
Signed-off-by: Manivannan Sadhasivam
[cristian: change binding doc file path, add file patterns for onkey and
poweroff drivers, fix ordering, add myself as co-maintainer]
Signed-off-by: Cristian Ciocaltea
---
Change
Add devicetree binding for Actions Semi ATC260x PMICs.
Signed-off-by: Cristian Ciocaltea
Reviewed-by: Rob Herring
---
Changes in v7:
- None
Changes in v6:
- None
Changes in v5:
- None
Changes in v4
- Added Reviewed-by from Rob
- Added support for ATC2603C LDO12 fixed regulator per Mark's
On Fri, 22 Jan 2021 at 12:49, Andrew Jeffery wrote:
>
> Randy found that with the following Kconfig settings we have duplicate
> definitions (e.g. __inittest()) in sdhci-of-aspeed due to competing
> module_init()/module_exit() calls from kunit and driver the itself.
>
> ```
> CONFIG_MMC_SDHCI_OF_A
On Mon, 25 Jan 2021 at 13:28, Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> Having both the driver and the unit test in the same module
> leads to a link failure because of the extra init/exit functions:
>
> drivers/mmc/host/sdhci-of-aspeed-test.c:98:1: error: redefinition of
> '__inittest'
>
submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Nicholas-Piggin/huge-vmalloc-mappings/20210126-143141
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
conf
On Mon 25-01-21 11:39:50, Jens Axboe wrote:
> On 1/25/21 11:35 AM, Paolo Valente wrote:
> >
> >
> >> Il giorno 25 gen 2021, alle ore 10:40, Stephen Rothwell
> >> ha scritto:
> >>
> >> Hi all,
> >>
> >> In commit
> >>
> >> d4fc3640ff36 ("block, bfq: set next_rq to waker_bfqq->next_rq in waker
Hi Alex, Cornelia and Jason,
thanks for the reviewing this.
On 1/26/2021 5:34 AM, Alex Williamson wrote:
On Mon, 25 Jan 2021 20:45:22 -0400
Jason Gunthorpe wrote:
On Mon, Jan 25, 2021 at 04:31:51PM -0700, Alex Williamson wrote:
We're supposed to be enlightened by a vendor driver that does
This patch adds support spi to MT6779 SOC
Silence indentation level warning reported by dt_binding_check in
order to reduce noise during routine checks.
$ make dt_binding_check
mt8192-mt6359-rt1015-rt5682.yaml:10:4: [warning] wrong indentation:
expected 2 but found 3 (indentation)
Signed-off-by: Robert Foss
---
.../bindings/sound/mt819
On Mon, Jan 25 2021 at 19:40, Mickaël Salaün wrote:
> After some bisecting, I found that commit 05a0302c3548 ("rtc: mc146818:
> Prevent reading garbage", this patch, introduced since v5.11-rc1) makes
> my VM hang at boot. Before this commit, I got this (and didn't notice)
> at every boot:
> rtc_cmo
From: mtk22786
this patch add spi host dts nodes for mt6779 IC.
Change-Id: If4a3cbb09843f472210b390352db4b9886f5c00c
Signed-off-by: Mason Zhang
---
arch/arm64/boot/dts/mediatek/mt6779.dtsi | 96
1 file changed, 96 insertions(+)
diff --git a/arch/arm64/boot/dts/mediate
@James
Hi James, please help to review this patch. Thank you very much. :)
On 2020/12/10 20:09, Xiaofei Tan wrote:
After the commit 8fcc4ae6faf8 ("arm64: acpi: Make apei_claim_sea()
synchronise with APEI's irq work") applied, do_sea() return directly
for user-mode if apei_claim_sea() handled any
On 1/20/21 8:40 PM, Michael Walle wrote:
> Add support for the Ebang EBAZ4205 board. This board was once used as a
> control board for a bitcoin mining device. Nowawdays it is sold as a cheap
> Zynq-7000 eval board.
>
> Michael Walle (3):
> dt-bindings: add ebang vendor prefix
> dt-bindings
On Thu, Jan 21, 2021 at 05:35:35PM +0100, Maxime Ripard wrote:
> Many drivers reference the plane->state pointer in order to get the
> current plane state in their atomic_update or atomic_disable hooks,
> which would be the new plane state in the global atomic state since
> _swap_state happened whe
Silence indentation level warning reported by dt_binding_check in
order to reduce noise during routine checks.
$ make dt_binding_check
mt8192-mt6359-rt1015-rt5682.yaml:10:4: [warning] wrong indentation:
expected 2 but found 3 (indentation)
Signed-off-by: Robert Foss
---
.../devicetree/bindings/
On !PREEMPT kernel, we can get below softlockup when doing stress
testing with creating and destroying block cgroup repeatly. The
reason is it may take a long time to acquire the queue's lock in
the loop of blkcg_destroy_blkgs(), thus we can use cond_resched()
instead of cpu_relax() to avoid this i
On Tue, Jan 26, 2021 at 12:20:19PM +, Srinivas Kandagatla wrote:
> +#define __soc_component_field_shift(x) (__builtin_ffs(x) - 1)
Why not have this be a static inline?
> +unsigned int snd_soc_component_read_field(struct snd_soc_component
> *component,
> +
On 12/01/21 19:10, Ben Gardon wrote:
+* May be acquired under the MMU lock in read mode or non-overlapping
+* with the MMU lock.
+*/
+ spinlock_t tdp_mmu_pages_lock;
Is this correct? My understanding is that:
- you can take tdp_mmu_pages_lock from a shared MMU
On 1/25/21 11:05 PM, Moritz Fischer wrote:
On Mon, Jan 25, 2021 at 02:56:27PM -0600, richard.g...@linux.intel.com wrote:
From: Richard Gong
Add authenticate-fpga-config property for FPGA bitstream authentication,
which makes sure a signed bitstream has valid signatures.
Signed-off-by: Rich
On 12/01/21 19:10, Ben Gardon wrote:
+ if (is_tdp_mmu_root(vcpu->kvm, vcpu->arch.mmu->root_hpa))
+ kvm_mmu_lock_shared(vcpu->kvm);
+ else
+ kvm_mmu_lock(vcpu->kvm);
Perhaps the better API would be kvm_mmu_lock/unlock_root; not exposing
kvm_mmu_lock/unloc
On Tue, 26 Jan 2021 at 09:52, Michal Hocko wrote:
>
> On Thu 21-01-21 19:19:21, Vlastimil Babka wrote:
> [...]
> > We could also start questioning the very assumption that number of cpus
> > should
> > affect slab page size in the first place. Should it? After all, each CPU
> > will
> > have one
On 1/13/21 8:38 PM, AngeloGioacchino Del Regno wrote:
> From: Martin Botka
>
> Add a driver for the multimedia clock controller found on SDM660
> based devices. This should allow most multimedia device drivers
> to probe and control their clocks.
>
> Signed-off-by: Martin Botka
> Co-develope
On Tue, Jan 26, 2021 at 02:02:40PM +0100, Wolfram Sang wrote:
> Hi Russell,
>
> > Those who cause breakage really should be the ones to look at patches
> > that fix their breakage.
>
> Does it mean you want an explicit ack from Thomas or that it should go
> via his tree?
What I'm saying is... do
With the new fscache API, the PageFsCache bit now indicates that the
page is being written to the cache and shouldn't be modified or released
until it's finished.
Change releasepage and invalidatepage to wait on that bit before
returning.
Signed-off-by: Jeff Layton
---
fs/ceph/addr.c | 9 ++
Convert ceph_readpages to ceph_readahead and make it use
netfs_readahead. With this we can rip out a lot of the old
readpage/readpages infrastructure.
Signed-off-by: Jeff Layton
---
fs/ceph/addr.c | 229 -
1 file changed, 34 insertions(+), 195 dele
commit 52f3fab0067d ("iommu/arm-smmu-v3: Don't reserve implementation
defined register space") only reserves the basic SMMU register space. So
the ECMDQ register space is not covered, it should be mapped again. Due
to the size of this ECMDQ resource is not fixed, depending on
SMMU_IDR6.CMDQ_CONTROL
The MODULE_SOFTDEP() gives user space a hint of the loading sequence. And
when command "modprobe arm_smmuv3_pmu" is executed, the arm_smmu_v3.ko is
automatically loaded in advance.
Signed-off-by: Zhen Lei
---
drivers/perf/arm_smmuv3_pmu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drive
The ARMv8.4 TTRem feature offers 3 levels of support when changing block
size without changing any other parameters that are listed as requiring
use of break-before-make.
With level 0 supported, software must use break-before-make to avoid the
possible hardware problems. With level 1 supported, be
As TTrem can be used when coalesce existing table mappings into a block
in guest stage-2 translation, so just support usage of it.
Signed-off-by: Yanan Wang
---
arch/arm64/kvm/hyp/pgtable.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/kvm/hyp/pgtable.c b/arch/arm64/kvm/hyp/pg
The ARMv8.4 architecture offers 3 levels of support when changing
block size without changing any other parameters that are listed
as requiring use of break-before-make. So get the current level
of TTRem supported by hardware and software can use corresponding
process when changing block size.
Sig
On Tue, Jan 26, 2021 at 1:27 AM Uwe Kleine-König wrote:
>
> Hello Masahiro,
>
> On 1/25/21 10:53 PM, Masahiro Yamada wrote:
> > On Mon, Jan 25, 2021 at 8:07 PM Uwe Kleine-König
> > wrote:
> >>
> >> Adding the -@ switch to dtc results in the binary devicetrees containing
> >> a list of symbolic r
Hi Moritz,
On 1/25/21 11:10 PM, Moritz Fischer wrote:
On Mon, Jan 25, 2021 at 02:56:26PM -0600, richard.g...@linux.intel.com wrote:
From: Richard Gong
Add authenticate-fpga-config property to support FPGA bitstream
authentication, which makes sure a signed bitstream has valid signatures.
S
Currently, addr_has_metadata() returns true for every address.
An invalid address (e.g. NULL) passed to the function when,
KASAN_HW_TAGS is enabled, leads to a kernel panic.
Make addr_has_metadata() return true for valid addresses only.
Note: KASAN_HW_TAGS support for vmalloc will be added with a
On Mon, Jan 25, 2021 at 11:40 PM wrote:
>
> From: Daniele Alessandrelli
>
> Add bindings for the Intel VPU IPC mailbox driver.
Sigh. DT list please so it's in my queue and automated checks run.
> Signed-off-by: Daniele Alessandrelli
> ---
> .../mailbox/intel,vpu-ipc-mailbox.yaml| 69 +
With the introduction of KASAN_HW_TAGS, kasan_report() currently assumes
that every location in memory has valid metadata associated. This is due
to the fact that addr_has_metadata() returns always true.
As a consequence of this, an invalid address (e.g. NULL pointer address)
passed to kasan_repor
With the introduction of KASAN_HW_TAGS, kasan_report() accesses the
metadata only when addr_has_metadata() succeeds.
Add a comment to make sure that the preconditions to the function are
explicitly clarified.
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Dmitry Vyukov
Cc: Leon Romanovsky
Cc
If migration of a VM with hugepages is canceled midway, KVM will adjust
the stage-2 table mappings back to block mappings. We currently use BBM
to replace the table entry with a block entry. Take adjustment of 1G block
mapping as an example, with BBM procedures, we have to invalidate the old
table
On Tue, Jan 26, 2021 at 09:33:40AM +, Zhang, Qiang wrote:
>
>
>
> 发件人: Uladzislau Rezki
> 发送时间: 2021年1月25日 21:49
> 收件人: Zhang, Qiang
> 抄送: Uladzislau Rezki; LKML; RCU; Paul E . McKenney; Michael Ellerman; Andrew
> Morton; Daniel Axtens; Frederic Weis
This patchset implements the asynchronous mode support for ARMv8.5-A
Memory Tagging Extension (MTE), which is a debugging feature that allows
to detect with the help of the architecture the C and C++ programmatic
memory errors like buffer overflow, use-after-free, use-after-return, etc.
MTE is bui
MTE provides a mode that asynchronously updates the TFSR_EL1 register
when a tag check exception is detected.
To take advantage of this mode the kernel has to verify the status of
the register at:
1. Context switching
2. Return to user/EL0 (Not required in entry from EL0 since the kernel
did
KASAN provides an asynchronous mode of execution.
Add reporting functionality for this mode.
Cc: Dmitry Vyukov
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Andrey Konovalov
Reviewed-by: Andrey Konovalov
Signed-off-by: Vincenzo Frascino
---
include/linux/kasan.h | 6 ++
mm/kasan/rep
Hi Paolo,
Any comments? Thanks!
B.R.
Yu
On Sat, Jan 16, 2021 at 08:21:00AM +0800, Yu Zhang wrote:
> In shadow page table, only leaf SPs may be marked as unsync.
> And for non-leaf SPs, we use unsync_children to keep the number
> of the unsynced children. In kvm_mmu_sync_root(), sp->unsync
> sh
Architectures supported by KASAN_HW_TAGS can provide a sync or async mode
of execution. On an MTE enabled arm64 hw for example this can be identified
with the synchronous or asynchronous tagging mode of execution.
In synchronous mode, an exception is triggered if a tag check fault occurs.
In asynch
Currently, the __is_lm_address() check just masks out the top 12 bits
of the address, but if they are 0, it still yields a true result.
This has as a side effect that virt_addr_valid() returns true even for
invalid virtual addresses (e.g. 0x0).
Fix the detection checking that it's actually a kerne
MTE provides an asynchronous mode for detecting tag exceptions. In
particular instead of triggering a fault the arm64 core updates a
register which is checked by the kernel after the asynchronous tag
check fault has occurred.
Add support for MTE asynchronous mode.
The exception handling mechanism
According to the SMMUv3 specification:
Each PMCG counter group is represented by one 4KB page (Page 0) with one
optional additional 4KB page (Page 1), both of which are at IMPLEMENTATION
DEFINED base addresses.
This means that the PMCG register spaces may be within the 64KB pages of
the SMMUv3 reg
v1 --> v2:
According to Robin Murphy's suggestion: https://lkml.org/lkml/2021/1/20/470
Don't reserve the PMCG register spaces, and reserve the entire SMMU register
space.
v1:
Since the PMCG may implement its resigters space(4KB Page0 and 4KB Page1)
within the SMMUv3 64KB Page0. In this case, when
Hi all,
This series enable CPU TTRem feature for stage-2 page table and a RFC is sent
for some comments, thanks.
The ARMv8.4 TTRem feature offers 3 levels of support when changing block
size without changing any other parameters that are listed as requiring use
of break-before-make. And I found th
this patch add spi host dts nodes for mt6779 IC.
Change-Id: If4a3cbb09843f472210b390352db4b9886f5c00c
Signed-off-by: Mason Zhang
---
arch/arm64/boot/dts/mediatek/mt6779.dtsi | 96
1 file changed, 96 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6779.dtsi
b/
701 - 800 of 2082 matches
Mail list logo
