Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
driver dependency into Kconfig as CONFIG_IMX_SCU must be
selected to support i.MX SCU SoC driver, also need to use
platform driver model to make sure IMX_SCU driver is probed
before i.MX SCU SoC driver.
With this patch, SoC info can
This patch selects CONFIG_IMX_SCU_SOC by default to support
i.MX system controller unit SoC info driver.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
On Thu, May 16, 2019 at 10:37 PM Greg KH wrote:
>
> On Fri, May 17, 2019 at 01:45:11PM +0900, Masahiro Yamada wrote:
> > On Fri, May 17, 2019 at 1:29 PM Masahiro Yamada
> > wrote:
> > >
> > > In the recent build test of linux-next, Stephen saw a build error
> > > caused by a broken
Dan Williams writes:
> On Wed, May 15, 2019 at 10:55 PM Vaibhav Jain wrote:
>>
>> Presently __bdev_dax_supported() checks if first sector of last
>> page ( last_page ) on the block device is aligned to page
>> boundary. However the code to compute 'last_page' assumes that there
>> are 8
On Fri, May 17, 2019 at 01:45:11PM +0900, Masahiro Yamada wrote:
> On Fri, May 17, 2019 at 1:29 PM Masahiro Yamada
> wrote:
> >
> > In the recent build test of linux-next, Stephen saw a build error
> > caused by a broken .tmp_versions/*.mod file:
> >
> > https://lkml.org/lkml/2019/5/13/991
> >
Hi Masahiro,
Thanks for this, looks good to me. Just a nit below.
On Fri, 17 May 2019 13:27:53 +0900 Masahiro Yamada
wrote:
>
> diff --git a/scripts/modules-check.sh b/scripts/modules-check.sh
> new file mode 100755
> index ..c875f6eab01e
> --- /dev/null
> +++
This patch adds USB dt nodes for LS1028A.
Signed-off-by: Ran Wang
---
Changes in v4:
- Move nodes to follow rule of unit-address in the address.
- Use macro to replace 'interrupts' values.
Changes in v3:
- Add space between label and node name.
- Add spcae with properties and '='.
-
On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> We are building the upstream kernel. There are a few patches, but
> nothing related to objtool.
>
> Unless you mean mainline/stable by upstream, I haven't tried that. We
> stick to LTS.
Please work and all of these issues fixed up in
PSCI spec define 1st parameter's bit 16 of function CPU_SUSPEND to
indicate CPU State Type: 0 for standby, 1 for power down. In this
case, we want to select standby for CPU idle feature. But current
setting wrongly select power down and cause CPU SUSPEND fail every
time. Need this fix.
Fixes:
From: Naveen Kumar Parna
Fixed the checkpatch error. Used "foo *bar" instead of "foo * bar"
Signed-off-by: Naveen Kumar Parna
---
drivers/char/bsr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/bsr.c b/drivers/char/bsr.c
index a6cef548e01e..d16ba62d03a0
On 16. 05. 19, 15:59, Michal Hocko wrote:
>> However, I tend to agree with Michal that (ab)using node[0].memcg_lrus
>> to check if a list_lru is memcg aware looks confusing. I guess we could
>> simply add a bool flag to list_lru instead. Something like this, may be:
>
> Yes, this makes much more
On 05/17/2019 09:38 AM, Jane Chu wrote:
> Some user who install SIGBUS handler that does longjmp out
What the longjmp about ? Are you referring to the mechanism of catching the
signal which was registered ?
> therefore keeping the process alive is confused by the error
> message
>
On Fri, May 17, 2019 at 1:29 PM Masahiro Yamada
wrote:
>
> In the recent build test of linux-next, Stephen saw a build error
> caused by a broken .tmp_versions/*.mod file:
>
> https://lkml.org/lkml/2019/5/13/991
>
> drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
> basename,
Hi Patrick,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0d74471924f2a01dcd32d154510c0500780b531a
commit: 524feb799408e5d45c6aa82763a9f52489d1e19f soc: add aspeed folder and
misc drivers
date: 3 weeks ago
From: Naveen Kumar Parna
According to checkpatch: EXPORT_SYMBOL(foo); should immediately follow its
function/variable.
This patch fixes the following checkpatch.pl issues in drivers/char/misc.c:
WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
Signed-off-by: Naveen
On 2019-05-15 1:43 p.m., Marcelo Tosatti wrote:
On Wed, May 15, 2019 at 11:42:56AM -0700, Ankur Arora wrote:
On 5/14/19 6:50 AM, Marcelo Tosatti wrote:
On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
On Wed, 8 May 2019 at 02:57, Marcelo Tosatti wrote:
Certain workloads perform
In the recent build test of linux-next, Stephen saw a build error
caused by a broken .tmp_versions/*.mod file:
https://lkml.org/lkml/2019/5/13/991
drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
basename, and there is a race in generating .tmp_versions/asix.mod
Kbuild has
On Thu, May 16, 2019 at 12:53:00PM -0500, Alan Tull wrote:
> On Thu, May 16, 2019 at 12:36 PM Alan Tull wrote:
> >
> > On Mon, Apr 29, 2019 at 4:12 AM Wu Hao wrote:
>
> Hi Hao,
>
> Most of this patchset looks ready to go upstream or nearly so with
> pretty straightforward changes . Patches 17
On Fri, May 17, 2019 at 8:01 AM Laura Abbott wrote:
>
> On 4/22/19 8:49 PM, Masahiro Yamada wrote:
> > This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
> > place. We need to eliminate potential issues beforehand.
> >
> > If it is enabled for s390, the following error is
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190516:
The kvm tree gained conflicts against Linus' tree.
Non-merge commits (relative to Linus' tree): 1023
1119 files changed, 27058 insertions
Hi Laura,
On Fri, May 17, 2019 at 7:55 AM Laura Abbott wrote:
> What gcc version was this tested with?
I use kernel.org toolchains
https://mirrors.edge.kernel.org/pub/tools/crosstool/
It is GCC 8.1
> We're still seeing errors on
> Fedora rawhide with gcc 9.1.1 on a version
>
Some user who install SIGBUS handler that does longjmp out
therefore keeping the process alive is confused by the error
message
"[188988.765862] Memory failure: 0x1840200: Killing
cellsrv:33395 due to hardware memory corruption"
Slightly modify the error message to improve clarity.
On Thu, May 16, 2019 at 12:35:27PM -0500, Alan Tull wrote:
> On Mon, Apr 29, 2019 at 4:12 AM Wu Hao wrote:
>
> It looks like this addressed the review comments. Adding my Ack. Is
> there anything else on this patch?
Nothing else, just addressed the review comments. : )
Thanks for the review
Enable SPI1 exposed on both Low and High speed expansion connectors
of Ficus. SPI1 has 3 different chip selects wired as below:
CS0 - Serial Flash (unpopulated)
CS1 - Low Speed expansion
CS2 - High Speed expansion
Signed-off-by: Manivannan Sadhasivam
---
Changes in v2:
* Used pin constants
Enable SPI0 and SPI4 exposed on the Low and High speed expansion
connectors of Rock960.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v2:
* Dropped the label property since it is not part of SPI binding
arch/arm64/boot/dts/rockchip/rk3399-rock960.dts | 10 ++
1 file changed, 10
On Thu, May 16, 2019 at 12:28:08PM -0500, Alan Tull wrote:
> On Mon, Apr 29, 2019 at 4:13 AM Wu Hao wrote:
>
> Hi Hao,
>
> >
> > This patch adds support for performance reporting private feature
> > for FPGA Management Engine (FME). Actually it supports 4 categories
> > performance counters,
Linus,
The following changes since commit 7a223e06b1a411cef6c4cd7a9b9a33c8d225b10e:
KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in
tracing (2019-04-16 15:38:08 +0200)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git
Hi Rob,
On Mon, May 13, 2019 at 01:02:46PM -0500, Rob Herring wrote:
> On Mon, May 06, 2019 at 03:35:32PM +0530, Manivannan Sadhasivam wrote:
> > Document devicetree binding for Avenger96 board.
> >
> > Signed-off-by: Manivannan Sadhasivam
> > ---
> >
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
Hi Kees,
On Thu, May 16, 2019 at 3:38 AM Kees Cook wrote:
>
> On Thu, May 16, 2019 at 02:55:02AM +0900, Masahiro Yamada wrote:
> >
> > On Thu, May 16, 2019 at 1:20 AM Kees Cook wrote:
> > >
> > > On Wed, May 15, 2019 at 04:53:15PM +0900, Masahiro Yamada wrote:
> > > > On Wed, May 15, 2019 at
By default, QorIQ SoC's RCPM register block is Big Endian. But
there are some exceptions, such as LS1088A and LS2088A, are Little
Endian. So add this optional property to help identify them.
Actually LS2021A and other Layerscapes won't totally follow Chassis
2.1, so separate them from powerpc
The NXP's QorIQ Processors based on ARM Core have RCPM module
(Run Control and Power Management), which performs all device-level
tasks associated with power management such as wakeup source control.
This driver depends on PM wakeup source framework which help to
collect wake information.
Some user might want to go through all registered wakeup sources
and doing things accordingly. For example, SoC PM driver might need to
do HW programming to prevent powering down specific IP which wakeup
source depending on. And is user's responsibility to identify if this
wakeup source he is
Hi Kees,
On Thu, May 16, 2019 at 3:31 AM Kees Cook wrote:
>
> On Thu, May 16, 2019 at 03:07:54AM +0900, Masahiro Yamada wrote:
> > On Wed, May 15, 2019 at 4:40 PM Masahiro Yamada
> > wrote:
> >
> > > $(Q)$(AWK) '!x[$$0]++' $^ > $(objtree)/modules.builtin
> > > diff --git
Hi, Bibby:
On Thu, 2019-05-16 at 17:02 +0800, Bibby Hsieh wrote:
> Define a instruction structure for gce driver to append command.
> This structure can make the client's code more readability.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/soc/mediatek/mtk-cmdq-helper.c | 113
Add regcache_mark_dirty before regcache_sync for power
of codec may be lost at suspend, then all the register
need to be reconfigured.
Fixes: 0c516b4ff85c ("ASoC: cs42xx8: Add codec driver support for
CS42448/CS42888")
Cc:
Signed-off-by: Shengjiu Wang
---
Changs in V2
- Don't split Fixes tag.
Hi Arnd,
-Original Message-
From: Arnd Bergmann
Sent: 2019年5月15日 16:05
To: Xiaowei Bao
Cc: Bjorn Helgaas ; Rob Herring ; Mark
Rutland ; Shawn Guo ; Leo Li
; Kishon ; Lorenzo Pieralisi
; gregkh ; M.h. Lian
; Mingkai Hu ; Roy Zang
; Kate Stewart ; Philippe
Ombredanne ; Shawn Lin ;
On 05/16/2019 04:27 PM, Mark Rutland wrote:
> On Thu, May 16, 2019 at 11:04:48AM +0530, Anshuman Khandual wrote:
>> On 05/15/2019 05:19 PM, Mark Rutland wrote:
>>> On Tue, May 14, 2019 at 02:30:07PM +0530, Anshuman Khandual wrote:
Memory removal from an arch perspective involves tearing
We are building the upstream kernel. There are a few patches, but
nothing related to objtool.
Unless you mean mainline/stable by upstream, I haven't tried that. We
stick to LTS.
On Thu, May 16, 2019 at 7:04 PM Josh Poimboeuf wrote:
>
> On Thu, May 16, 2019 at 11:20:54PM +0200, Miguel Ojeda
Hi
> Add regcache_mark_dirty before regcache_sync for power of codec may be
> lost at suspend, then all the register need to be reconfigured.
>
> Fixes: 0c516b4ff85c ("ASoC: cs42xx8: Add codec driver support for
> CS42448/CS42888")
The Fixes tag is split, will send v2.
Best regards
Wang
Propagation of new syscalls to other architectures + cosmetical
change from Christian (fscontext didn't follow the convention for anon
inode names).
What is _not_ included is cloexec changes - I really don't see
the benefits for the cloexec-by-default for new syscalls, when
There is chip errata ERR008000, the reference doc is
(https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf),
The issue is "While using ESAI transmit or receive and
an underrun/overrun happens, channel swap may occur.
The only recovery mechanism is to reset the ESAI."
In this commit add a tasklet to
On Thu, 16 May 2019 19:17:17 PDT (-0700), Linus Torvalds wrote:
On Thu, May 16, 2019 at 5:27 PM Palmer Dabbelt wrote:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-5.2-mw1
Oh no no no.
You're creating a binary file from your build or
By default, QorIQ SoC's RCPM register block is Big Endian. But
there are some exceptions, such as LS1088A and LS2088A, are Little
Endian. So add this optional property to help identify them.
Actually LS2021A and other Layerscapes won't totally follow Chassis
2.1, so separate them from powerpc
The NXP's QorIQ Processors based on ARM Core have RCPM module
(Run Control and Power Management), which performs all device-level
tasks associated with power management such as wakeup source control.
This driver depends on PM wakeup source framework which help to
collect wake information.
Some user might want to go through all registered wakeup sources
and doing things accordingly. For example, SoC PM driver might need to
do HW programming to prevent powering down specific IP which wakeup
source depending on. And is user's responsibility to identify if this
wakeup source he is
Hi, Thomas,
On Thu, May 16, 2019 at 03:02:57PM +0200, Thomas Huth wrote:
> So far the KVM selftests are compiled without any compiler warnings
> enabled. That's quite bad, since we miss a lot of possible bugs this
> way. Let's enable at least "-Wall" and some other useful warning flags
> now.
>
On Sun, May 12, 2019 at 08:38:22AM +, Anson Huang wrote:
> The imx_scu_irq_group_enable() is normally called during module driver
> probe phase to enable SCU group irq, if SCU IPC is NOT ready, below
> dump will show out:
>
> [0.933001] Hardware name: Freescale i.MX8QXP MEK (DT)
> [
Hi
Do I need to resend the patch?
Best regards
Wang shengjiu
>
> In commit
>
> b06c58c2a1ee ("ASoC: fsl_asrc: Fix the issue about unsupported rate")
>
> Fixes tag
>
> Fixes: fff6e03c7b65 ("ASoC: fsl_asrc: add support for 8-30kHz
>
> has these problem(s):
>
> - Subject has leading
ping...
On 2019/4/23 22:56, Yue Haibing wrote:
> From: YueHaibing
>
> KASAN report this:
>
> walkera0701: failed to allocate input device
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP KASAN
On Thu, May 09, 2019 at 03:06:57PM +0800, Chuanhua Han wrote:
> ls1028a platform uses sp805 watchdog, and use 1/16 platform clock as
> timer clock, this patch fix device tree node.
>
> Signed-off-by: Zhang Ying-22455
> Signed-off-by: Chuanhua Han
> ---
>
On Tue, Apr 23, 2019 at 5:40 AM Alexandre Mergnat wrote:
>
> PixArt Imaging Inc. is expertized in CMOS image sensors (CIS),
> capacitive touch controllers and related imaging application development.
>
> Signed-off-by: Alexandre Mergnat
> ---
>
On Wed, May 08, 2019 at 01:53:10PM +, Pramod Kumar wrote:
> ls1046afrwy board is based on nxp ls1046a SoC.
>
> Signed-off-by: Vabhav Sharma
> Signed-off-by: Pramod Kumar
Please have a subject prefix like 'arm64: dts: ...'
Shawn
> ---
> arch/arm64/boot/dts/freescale/Makefile| 1
On Wed, May 08, 2019 at 01:53:08PM +, Pramod Kumar wrote:
> Add "fsl,ls1046a-frwy" bindings for ls1046afrwy board based on ls1046a SoC
>
> Signed-off-by: Vabhav Sharma
> Signed-off-by: Pramod Kumar
Sorry. I do not take patch from message using base64 encoding.
Shawn
> ---
>
On Wed, May 15, 2019 at 11:35 AM Fabrizio Castro
wrote:
>
> Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree
> vendor prefixes as "hoperun".
>
> Website: http://www.hoperun.com/en
>
> Signed-off-by: Fabrizio Castro
> Reviewed-by: Chris Paterson
>
> ---
> v1->v2:
> * No change
On Tue, May 14, 2019 at 8:28 AM Angus Ainslie (Purism) wrote:
>
> Add an entry for Purism, SPC
>
> Signed-off-by: Angus Ainslie (Purism)
> Reviewed-by: Rob Herring
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
I've converted this file to
The pull request you sent on Thu, 16 May 2019 16:04:29 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> tags/clk-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/815d469d8c9a3360ee0a8b7857dd95352a6c7bde
Thank you!
--
Deet-doot-dot,
The pull request you sent on Thu, 16 May 2019 15:52:38 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.2-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4c7b63a32d54850a31a00f22131db417face70e4
Thank you!
The pull request you sent on Thu, 16 May 2019 15:43:27 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
> tags/devicetree-for-5.2-part2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9cbda1bddb4c561f3a7360d36ce13a73bb02bfeb
Thank you!
--
The pull request you sent on Thu, 16 May 2019 15:38:10 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.2-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5f3ab27b9eb7f1b97e6d4460ac4e494588e09f0c
Thank you!
--
Deet-doot-dot, I am a
On Thu, May 16, 2019 at 5:27 PM Palmer Dabbelt wrote:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
> tags/riscv-for-linus-5.2-mw1
Oh no no no.
You're creating a binary file from your build or something like that:
> modules.builtin.modinfo
On Wed, May 08, 2019 at 06:46:37AM +, Ran Wang wrote:
> This patch adds USB dt nodes for LS1028A.
>
> Signed-off-by: Ran Wang
> ---
> Changes in v3:
> - Add space between label and node name.
> - Add spcae with properties and '='.
> - Add SoC specific compatible.
>
> Changes in v2:
>
On 2019-05-15 6:07 p.m., Wanpeng Li wrote:
On Thu, 16 May 2019 at 02:42, Ankur Arora wrote:
On 5/14/19 6:50 AM, Marcelo Tosatti wrote:
On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
On Wed, 8 May 2019 at 02:57, Marcelo Tosatti wrote:
Certain workloads perform poorly on KVM
On Thu, May 16, 2019 at 11:20:54PM +0200, Miguel Ojeda wrote:
> > mm/slub.o: warning: objtool: init_cache_random_seq()+0x36: sibling
> > call from callable instruction with modified stack frame
> > mm/slub.o: warning: objtool: slab_out_of_memory()+0x3b: sibling call
> > from callable instruction
Hi, Bibby:
On Thu, 2019-05-16 at 17:02 +0800, Bibby Hsieh wrote:
> tcmdq driver provide a function that get the relationship
What is 'tcmdq'?
> of sub system number from device node for client.
> add specification for #subsys-cells, mediatek,gce-subsys.
The property name is
From: Rob Clark
This is essentialy a squash of a bunch of history of cheza dt updates
from chromium kernel, some of which were themselves squashes of history
from older chromium kernels.
I don't claim any credit other than wanting to more easily boot upstream
kernel on cheza to have an easier
FAST_DEC_LOOP was introduced from LZ4 1.9[1].
This change would be introduce 10% on decompress operation
according to LZ4 benchmark result on X86 devices.
Meanwhile, LZ4 with FAST_DEC_LOOP could get improvements,
however clang compiler has downgrade if FAST_DEC_LOOP enabled.
So FAST_DEC_LOOP only
Hi, Bibby:
On Thu, 2019-05-16 at 17:02 +0800, Bibby Hsieh wrote:
> GCE cannot know the register base address, this function
> can help cmdq client to get the relationship of subsys
> and register base address.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/soc/mediatek/mtk-cmdq-helper.c | 25
On Tue, May 07, 2019 at 07:43:37AM +, Ran Wang wrote:
> PSCI spec define 1st parameter's bit 16 of function CPU_SUSPEND to
> indicate CPU State Type: 0 for standby, 1 for power down. In this
> case, we want to select standby for CPU idle feature. But current
> setting wrongly select power down
On 5/16/19 7:34 AM, Ken Goldman wrote:
But outside the client machine this key id is not sufficient to
uniquely determine which key the signature corresponds to.
Why is this not sufficient?
In my implementation, I create a lookup table at the attestation service
that maps the 4-byte IMA log
On Thu, May 16, 2019 at 6:06 PM Xing, Cedric wrote:
>
> > From: Andy Lutomirski [mailto:l...@kernel.org]
> >
> > On Thu, May 16, 2019 at 3:23 PM Xing, Cedric
> > wrote:
> > >
> > > Hi Andy,
> > >
> > > > > SIGSTRUCT isn't necessarily stored on disk so may not always have
> > a fd.
> > > > How
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
tools/testing/selftests/kvm/dirty_log_test.c
between commit:
76d58e0f07ec ("KVM: fix KVM_CLEAR_DIRTY_LOG for memory slots of unaligned
size")
from Linus' tree and commit:
65c4189de8c1 ("KVM: fix KVM_CLEAR_DIRTY_LOG
On Sun, May 12, 2019 at 10:02:10AM +, Anson Huang wrote:
> i.MX6SL's KPP and WDOG use IMX6SL_CLK_IPG as clock root,
> assign IMX6SL_CLK_IPG to them instead of IMX6SL_CLK_DUMMY.
>
> Signed-off-by: Anson Huang
> Reviewed-by: Dong Aisheng
Applied both ,thanks.
On Thu, May 16, 2019 at 03:02:18PM -0700, Florian Fainelli wrote:
> On 5/16/19 12:55 PM, Nikunj Kela (nkela) wrote:
> >
> >
> > On 5/16/19, 12:35 PM, "Jeff Kirsher" wrote:
> >
> > On Wed, 2019-05-08 at 23:14 +, Nikunj Kela wrote:
> >>> Some of the broken NICs don't have EEPROM
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/paging_tmpl.h
between commit:
73b0140bf0fe ("mm/gup: change GUP fast to use flags rather than a write
'bool'")
from Linus' tree and commit:
bd53cb35a3e9 ("X86/KVM: Handle PFNs outside of kernel reach when
> From: Andy Lutomirski [mailto:l...@kernel.org]
>
> On Thu, May 16, 2019 at 3:23 PM Xing, Cedric
> wrote:
> >
> > Hi Andy,
> >
> > > > SIGSTRUCT isn't necessarily stored on disk so may not always have
> a fd.
> > > How about the following?
> > > > void *ss_pointer = mmap(sigstruct_fd,
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
Documentation/virtual/kvm/api.txt
between commit:
dbcdae185a70 ("Documentation: kvm: fix dirty log ioctl arch lists")
from Linus' tree and commit:
d7547c55cbe7 ("KVM: Introduce KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2")
from
Jeff discovered that performance improves from ~375K iops to ~519K iops
on a simple psync-write fio workload when moving the location of 'struct
page' from the default PMEM location to DRAM. This result is surprising
because the expectation is that 'struct page' for dax is only needed for
third
On Thu, May 16, 2019 at 3:23 PM Xing, Cedric wrote:
>
> Hi Andy,
>
> > > SIGSTRUCT isn't necessarily stored on disk so may not always have a fd.
> > How about the following?
> > > void *ss_pointer = mmap(sigstruct_fd, PROT_READ,...);
> > > ioctl(enclave_fd, SGX_INIT_THE_ENCLAVE, ss_pointer);
> >
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-5.2-mw1
for you to fetch changes up to
On Thu, May 16, 2019 at 5:03 PM Sean Christopherson
wrote:
>
> On Wed, May 15, 2019 at 11:27:04AM -0700, Andy Lutomirski wrote:
> > Here's a very vague proposal that's kind of like what I've been
> > thinking over the past few days. The SGX inode could track, for each
> > page, a
The pull request you sent on Thu, 16 May 2019 17:40:05 +0200:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.2-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1d9d7cbf28a1c2f84f2a0224466f8eb5f0a62ace
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 17 May 2019 00:02:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/afs-fixes-b-20190516
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0d74471924f2a01dcd32d154510c0500780b531a
Tha
The pull request you sent on Fri, 17 May 2019 00:00:21 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/afs-fixes-20190516
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fefb2483dc10c736e4235984fed4f3a61c99e1c2
Thank you!
--
On Thu, May 16, 2019 at 4:00 PM David Howells wrote:
>
> Could you pull this series please?
I've pulled this, but I'm seriously considering just stopping pulling
from you entirely.
Not only is this late in the merge window, EVERY SINGLE commit I
pulled from you is from within a day or two.
And
On Wed, May 15, 2019 at 11:27:04AM -0700, Andy Lutomirski wrote:
> Here's a very vague proposal that's kind of like what I've been
> thinking over the past few days. The SGX inode could track, for each
> page, a "safe-to-execute" bit. When you first open /dev/sgx/enclave,
> you get a blank
On 5/16/2019 2:51 PM, Dan Williams wrote:
On Thu, May 16, 2019 at 9:45 AM Jane Chu wrote:
Hi,
I'm able to reproduce the panic below by running two sets of ndctl
commands that actually serve legitimate purpose in parallel (unlike
the brute force experiment earlier), each set in a indefinite
On Thu, May 16, 2019 at 11:42:58AM -0700, Linus Torvalds wrote:
On Thu, May 16, 2019 at 11:39 AM Greg KH wrote:
Thanks, I'll work on that later tonight...
Note that it probably is almost entirely impossible to trigger the
problem in practice, so it's not like this is a particularly
Hi,
We found a failure with selftests/bpf/tests_prog in test_stacktrace_map (on
bpf/master
branch).
After digging into the code, we found that perf_callchain_kernel() is giving
empty
callchain for tracepoint sched/sched_switch. And it seems related to commit
This patch addresses below two issues and prepares the code to address
3rd issue listed below.
1. mdev device is placed on the mdev bus before it is created in the
vendor driver. Once a device is placed on the mdev bus without creating
its supporting underlying vendor device, mdev driver's
If device is removal is initiated by two threads as below, mdev core
attempts to create a syfs remove file on stale device.
During this flow, below [1] call trace is observed.
cpu-0cpu-1
--
As we would like to use mdev subsystem for wider use case as
discussed in [1], [2] apart from an offline discussion.
This use case is also discussed with wider forum in [4] in track
'Lightweight NIC HW functions for container offload use cases'.
This series is prep-work and improves vfio/mdev
In following sequences, child devices created while removing mdev parent
device can be left out, or it may lead to race of removing half
initialized child mdev devices.
issue-1:
cpu-0 cpu-1
- -
> > > There is a problem here though. Usually the enclave itself is just a
> > > loader that then loads the application from outside source and
> > > creates the executable pages from the content.
> > >
> > > A great example of this is Graphene that bootstraps unmodified Linux
> > > applications
This is a re-post of the last 3 patches of a series I posted earlier
at:
https://lkml.kernel.org/r/20190418001356.124334-1-diand...@chromium.org
The first two patches were applied but the last three weren't because
they didn't apply at the time. They apply fine now so are ready to
land.
If the 'snps,need-phy-for-wake' is set in the device tree then:
- We know that we can wakeup, so call device_set_wakeup_capable().
The USB core will use this knowledge to enable wakeup by default.
- We know that we should keep the PHY on during suspend if something
on our root hub needs
The following changes since commit c1157f60d72e8b20efc670cef28883832f42406c:
Merge branch 'clk-parent-rewrite-1' into clk-next (2019-05-07 11:46:13 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-for-linus
for you to
On 4/22/19 8:49 PM, Masahiro Yamada wrote:
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for s390, the following error is reported:
In file included from arch/s390/crypto/des_s390.c:19:
ailable in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
tags/afs-fixes-b-20190516
for you to fetch changes up to 39db9815da489b47b50b8e6e4fc7566a77bd18bf:
afs: Fix application of the results of a inline bulk status fetc
tags/afs-fixes-20190516
for you to fetch changes up to fd711586bb7d63f257da5eff234e68c446ac35ea:
afs: Fix double inc of vnode->cb_break (2019-05-16 16:25:21 +0100)
AFS fi
1 - 100 of 884 matches
Mail list logo
