On Thu, May 16, 2019 at 09:51:03AM +0300, Jarkko Sakkinen wrote:
> On Thu, May 16, 2019 at 08:07:05AM +0300, Jarkko Sakkinen wrote:
> > On Wed, May 15, 2019 at 07:27:02AM -0700, Andy Lutomirski wrote:
> > >
> > > > On May 15, 2019, at 4:00 AM, Jarkko Sakkinen
> > > > wrote:
> > > >
> > > >> On
Hi Greg, Ben,
On Wed, May 15, 2019 at 1:12 PM Greg Kroah-Hartman
wrote:
> From: Josh Poimboeuf
>
> commit 98af8452945c55652de68536afdde3b520fec429 upstream.
>
> Keeping track of the number of mitigations for all the CPU speculation
> bugs has become overwhelming for many users. It's getting mor
Currently, if the user specifies an unsupported mitigation strategy on
the kernel command line, it will be ignored silently. The code will
fall back to the default strategy, possibly leaving the system more
vulnerable than expected.
This may happen due to e.g. a simple typo, or, for a stable kern
On 16.05.19 02:42, Dan Williams wrote:
> On Wed, May 15, 2019 at 11:12 AM Pavel Tatashin
> wrote:
>>
>>> Hi Pavel,
>>>
>>> I am working on adding this sort of a workflow into a new daxctl command
>>> (daxctl-reconfigure-device)- this will allow changing the 'mode' of a
>>> dax device to kmem, onli
Commit-ID: 88640e1dcd089879530a49a8d212d1814678dfe7
Gitweb: https://git.kernel.org/tip/88640e1dcd089879530a49a8d212d1814678dfe7
Author: Andy Lutomirski
AuthorDate: Tue, 14 May 2019 13:24:39 -0700
Committer: Ingo Molnar
CommitDate: Thu, 16 May 2019 09:05:11 +0200
x86/speculation/mds: Re
Commit-ID: 9d8d0294e78a164d407133dea05caf4b84247d6a
Gitweb: https://git.kernel.org/tip/9d8d0294e78a164d407133dea05caf4b84247d6a
Author: Andy Lutomirski
AuthorDate: Tue, 14 May 2019 13:24:40 -0700
Committer: Ingo Molnar
CommitDate: Thu, 16 May 2019 09:05:12 +0200
x86/speculation/mds: Im
Add bluetooth vbat and vddio power supplies
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-g12a-sei510.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a-sei510.dts
b/arch/arm64/boot/dts/amlogic/meson-g12a-sei510.dts
index 61fb30
On Wed, 15 May 2019, Andy Lutomirski wrote:
> On Wed, May 15, 2019 at 3:46 PM James Morris wrote:
> >
> > You could try user.sigstruct, which does not require any privs.
> >
>
> I don't think I understand your proposal. What file would this
> attribute be on? What would consume it?
It would b
This patch adds dt binding header for mediatek,mt7621-pll which
was added in:
commit e6046b5e69a0 ("MIPS: ralink: fix cpu clock of mt7621 and add dt clk
devices")
Signed-off-by: Weijie Gao
Signed-off-by: Chuanhong Guo
---
checkpatch.pl shows a warning that the line referencing old commit
is ov
From: Finley Xiao
>From Rockchips fractional divider usage, some clocks can be generated
by fractional divider, but the input clock frequency of fractional
divider should be less than a specified value.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk-px30.c
1. Support for some new features
2. fix up some error
Chang in V2:
[PATCH v2 5/6] : fix up the Register error, and add delay.
Elaine Zhang (4):
clk: rockchip: fix up the frac clk get rate error
clk: rockchip: add a clock-type for muxes based in the pmugrf
clk: rockchip: add pll up and down
+Tobin C. Harding
On Wed, May 15, 2019 at 5:24 PM Uladzislau Rezki wrote:
>
> Hello, Andrew.
>
> > An earlier version of this patch was accused of crashing the kernel:
> >
> > https://lists.01.org/pipermail/lkp/2019-April/010004.html
> >
> > does the v4 series address this?
> I tried before to n
Hi
Reviewed-by: Pierre-Yves MORDRET
Thanks
Regards
On 5/15/19 5:09 PM, Fabrice Gasnier wrote:
> During probe, return the "get_irq" error value instead of -EINVAL which
> allows the driver to be deferred probed if needed.
> Fix also the case where of_irq_get() returns a negative value.
> Note :
If setting freq is not support in rockchip_pll_rate_table,
It can calculate and set pll params by auto.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk-pll.c | 215 ++---
1 file changed, 200 insertions(+), 15 deletions(-)
diff --git a/drivers/clk/roc
set pll sequence:
->set pll to slow mode or other plls
->set pll down
->set pll params
->set pll up
->wait pll lock status
->set pll to normal mode
To slove the system error:
wait_pll_lock: timeout waiting for pll to lock
pll_set_params: pll update u
Rockchip socs often have some tiny number of muxes not controlled from
the core clock controller but through bits set in the pmugrf.
Use MUXPMUGRF() to cover this special clock-type.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk.c | 9 +
drivers/clk/rockchip/clk.h | 17 ++
From: Finley Xiao
The div offset of some clocks are different from their mux offset
and the COMPOSITE clock-type require that div and mux offset are
the same, so add a new COMPOSITE_DIV_OFFSET clock-type to handle that.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
drivers/clk/ro
support fractional divider with only one level parent clock
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/clk/rockchip/clk.c b/drivers/clk/rockchip/clk.c
index e04bf300ea0a..0256a99f06f3
snip
> >
> > Can you drop the patch?
>
> Yes, now dropped. Sasha, I think I did this same thing in the past :)
Thanks, I remember I probably reported same thing in the past too :)
Jack
On Mai 07 2019, Palmer Dabbelt wrote:
> LMK if you, or anyone else, has a preference. I'm assuming this will go in
> through my tree, so I've picked up my version for now :)
You did?
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4
On Tue, May 14, 2019 at 05:26:25PM -0600, Shuah Khan wrote:
> Hi Kelsey,
>
> On 5/11/19 10:57 PM, Kelsey Skunberg wrote:
> > Create /selftests/pidfd/.gitignore which holds the following file name
> > created after compiling:
>
> This patch generates the following checkpatch warning.
>
> WARNING:
On Wed 15-05-19 17:15:57, Greg KH wrote:
> On Wed, May 15, 2019 at 04:51:51PM +0200, Michal Hocko wrote:
> > [Cc Suren and Minchan - the email thread starts here
> > 20190514131654.25463-1-oleksa...@redhat.com]
> >
> > On Wed 15-05-19 08:53:11, Michal Hocko wrote:
> > [...]
> > > I will try to co
On Thu, 16 May 2019, Geert Uytterhoeven wrote:
> Currently, if the user specifies an unsupported mitigation strategy on
> the kernel command line, it will be ignored silently. The code will
> fall back to the default strategy, possibly leaving the system more
> vulnerable than expected.
Honestly
On Wed, May 15, 2019 at 04:24:00PM +0100, Stefan Hajnoczi wrote:
> On Tue, May 07, 2019 at 02:25:43PM +0200, Stefano Garzarella wrote:
> > Hi Jorge,
> >
> > On Mon, May 06, 2019 at 01:19:55PM -0700, Jorge Moreira Broche wrote:
> > > > On Wed, May 01, 2019 at 03:08:31PM -0400, Stefan Hajnoczi wrote
On Thu, May 16, 2019 at 09:47:13AM +0200, Michal Hocko wrote:
> On Wed 15-05-19 17:15:57, Greg KH wrote:
> > On Wed, May 15, 2019 at 04:51:51PM +0200, Michal Hocko wrote:
> > > [Cc Suren and Minchan - the email thread starts here
> > > 20190514131654.25463-1-oleksa...@redhat.com]
> > >
> > > On W
Indeed those CPU resources are shared between sibling hyperthreads on same CPU
core.
There is currently no mechanism merged upstream to completely mitigate
SMT-enabled scenarios.
Note that this is also true for L1TF.
There are several proposal to address this but they are still in early research
If spi_register_master fails in spi_bitbang_start
because device_add failure, We should return the
error code other than 0, otherwise calling
spi_bitbang_stop may trigger NULL pointer dereference
like this:
BUG: KASAN: null-ptr-deref in __list_del_entry_valid+0x45/0xd0
Read of size 8 at addr 0
On 5/15/2019 9:47 PM, parna.naveenku...@gmail.com wrote:
From: Naveen Kumar Parna
checkpatch.pl does not like assignment in if condition
Signed-off-by: Naveen Kumar Parna
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
Changes in v3:
The first patch has an extra space in if statement, so
Add an enum to formalize lock types, as those type values now matter.
In order to make:
LOCK_TYPE_READ & LOCK_TYPE_RECURSIVE != 0
The recursive-read type is set to 3 as opposed to the current 2.
Signed-off-by: Yuyang Du
---
include/linux/lockdep.h | 45 +
Direct dependency needs to keep track of its locks' read-write types. A
union field is added to lock_list struct so the type is stored there as
this:
lock_type[1] (u16), lock_type[0] (u16)
or:
dep_type (int)
where value:
0: exclusive / write
1: read
2
Hi Peter and Ingo,
Historically, the read-write lock (recursive-read locks included) is not
well supported in lockdep. This patchset attempts to solve this problem
sound and complete.
The bulk of the algorithm is in patch #10, which is actually not complex at
all. Hopefully, it simply works.
Now
A read-write lock is different from an exclusive lock in that read locks
can be concurrent, while a write lock is essentially the same as an
exclusive lock.
Read-write locks have not been well supported for deadlock detection so
far. This patch series designs and implements an algorithm to add thi
Next lock to acquire has the lock type set already. There is no need to
reassign it when it is recursive read. No functional change.
Signed-off-by: Yuyang Du
---
kernel/locking/lockdep.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
With read-write lock support, some read-write lock cases need to be updated,
specifically, some read-lock involved deadlocks are actually not deadlocks.
Hope I am not wildly wrong.
Signed-off-by: Yuyang Du
---
lib/locking-selftest.c | 44 +---
1 file chang
Since in graph search, multiple matches may be needed, a matched lock
needs to rejoin the search for another match, thereby introduce
mark_lock_unaccessed().
Signed-off-by: Yuyang Du
---
kernel/locking/lockdep.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/kernel/locking/lockdep.
Now that we support recursive read locks, a previously failed case:
| spin |wlock |rlock |mutex | wsem | rsem |
---
On Wed, May 15, 2019 at 11:15:36PM +0530, Hariprasad Kelam wrote:
> @@ -1042,7 +1042,7 @@ sint sta2ap_data_frame(
> }
>
> *psta = rtw_get_stainfo(pstapriv, pattrib->src);
> - if (*psta == NULL) {
> + if (!*psta == NULL) {
^^^
Lock chain needs to include information about the read-write lock type. To
that end, introduce:
chain_hlocks_type[MAX_LOCKDEP_CHAIN_HLOCKS]
in addition to:
chain_hlocks[MAX_LOCKDEP_CHAIN_HLOCKS]
Signed-off-by: Yuyang Du
---
kernel/locking/lockdep.c | 9 +
1 file change
When computing a chain's hash key, we need to consider a held lock's type,
so the additional data to use Jenkins hash algorithm is a composite of the
new held lock's lock class index (lower 16 bits) and its read-write type
(higher 16 bits) as opposed to just class index before:
held lock t
Deadlock checks are performed at two places:
- Within current's held lock stack, check for lock recursion deadlock.
- Within dependency graph, check for lock inversion deadlock.
Rename the two relevant functions for later use. Plus, with read locks,
dependency circle in graph is not a sufficien
Now we are good to finally support recursive read locks.
This is done simply by adding the dependency that has recursive locks to the
graph, which previously is skipped.
The reason is plainly simple:
(a). Recursive read lock differs from read lock only inside a task.
(b). check_deadlock_curr
- find_lock_in_path() tries to find whether a lock class is in the path.
- find_next_dep_in_path() returns the next dependency after a
given dependency in the path.
Signed-off-by: Yuyang Du
---
kernel/locking/lockdep.c | 31 +++
1 file changed, 31 insertions(+)
Add a macro LOCK_TYPE_NEST for nest lock type and mark the nested lock in
check_deadlock_current(). Unlike the other LOCK_TYPE_* enums, this lock type
is used only in lockdep.
No functional change.
Signed-off-by: Yuyang Du
---
kernel/locking/lockdep.c | 7 +--
kernel/locking/lockd
With read locks, circle is not sufficient condition for a deadlock. As a
result, we need to continue the search after a match but the match is not
wanted. __bfs() is adjusted to that end. The basic idea is to enqueue a
node's children before matching the node.
No functional change.
Signed-off-by:
When adding a dependency, if the dependency exists - be it direct or
indirect - the dependency's read-write type may be updated.
We can keep all different-typed dependencies, but for simplicity we just
"upgrade" lock types if possible, making them more exlusive (in the order:
recursive read -> rea
Lets make sure our 8 cases can be correctly handled. In contrast, before
this patchset, these 8 cases have 24 failures:
| spin |wlock |rlock |mutex | wsem | rsem |
---
We have a lockdep warning:
WARNING: possible irq lock inversion dependency detected
5.1.0-rc7+ #141 Not tainted
kworker/8:2/328 just changed the state of lock:
07f1
Hi Hans,
On 5/14/19 11:54 AM, Hans Verkuil wrote:
> Hi Stanimir,
>
> On 4/12/19 5:59 PM, Stanimir Varbanov wrote:
>> This changes v4l2_pix_format and v4l2_plane_pix_format sizeimage
>> field description to allow v4l clients to set bigger image size
>> in case of variable length compressed data.
>
1. Add calibrated sample data support
2. Use of_match_table to decide each platform's
feature set
Signed-off-by: Chun-Hung Wu
---
drivers/iio/adc/mt6577_auxadc.c | 54 +++--
1 file changed, 41 insertions(+), 13 deletions(-)
diff --git a/drivers/iio/adc/mt6
Add compatible node for mt6765 auxadc
Signed-off-by: Chun-Hung Wu
---
Documentation/devicetree/bindings/iio/adc/mt6577_auxadc.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/adc/mt6577_auxadc.txt
b/Documentation/devicetree/bindings/iio/adc/mt6577_au
Move auxadc platform_driver_register() from module_init
to subsys_initcall because auxadc user drivers
are all moudle drivers, need to gurantee
auxadc driver ready before module_init.
Signed-off-by: Chun-Hung Wu
---
drivers/iio/adc/mt6577_auxadc.c | 14 +-
1 file changed, 13 insert
This patch adds support of auxadc to MT6765 SoC.
Chun-Hung Wu (4):
dt-bindings: iio: adc: mediatek: Add document for mt6765
iio: adc: mediatek: mt6765 upstream driver
iio: adc: mediatek: SET_LATE_SYSTEM_SLEEP_PM_OPS support
iio: auxadc: mediatek: change to subsys_initcall
.../devicetree/
Move suspend/resume to late_suspend and
early_resume to gurantee users can use auxadc
driver at suspend/resume stage.
Signed-off-by: Chun-Hung Wu
---
drivers/iio/adc/mt6577_auxadc.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/adc/mt6577_auxadc.c b/dri
On 11.05.2019 00:32, Alexandre Belloni wrote:
> On 10/05/2019 11:23:31+, claudiu.bez...@microchip.com wrote:
>> From: Claudiu Beznea
>>
>> Different IPs uses different bit offsets in registers for the same
>> functionality, thus adapt the driver to support this.
>>
>> Signed-off-by: Claudiu
* Jiri Kosina wrote:
> On Thu, 16 May 2019, Geert Uytterhoeven wrote:
>
> > Currently, if the user specifies an unsupported mitigation strategy on
> > the kernel command line, it will be ignored silently. The code will
> > fall back to the default strategy, possibly leaving the system more
>
> On 4/16/19 3:54 PM, Rodin, Michael (Ferchau; ADITG/ESM1) wrote:
> > Hi,
> >
> > I would like to ask several questions regarding the documentation of the
> enum "v4l2_field" [1].
> > These questions came up during my investigations of issues with
> > interaction between the gstreamer plugin v4l2sr
On 2019/05/15 19:55, Petr Mladek wrote:
>> +if (!stamp) {
>> +stamp = jiffies;
>> +if (!stamp)
>> +stamp++;
>> +t->killed_time = stamp;
>> +return;
>> +}
>
> I might be too dumb but the above code looks pretty tricky to me
Hi Nicholas,
On Thu, May 16, 2019 at 04:13:17PM +1000, Nicholas Piggin wrote:
>
> > The motivation behind this patch was a HPC customer issue where they
> > were observing some CPUs in the core getting stuck at stop0_lite
> > state, thereby lowering the performance on the other CPUs of the core
On Thu, May 16, 2019 at 9:57 AM YueHaibing wrote:
> If spi_register_master fails in spi_bitbang_start
> because device_add failure, We should return the
> error code other than 0, otherwise calling
> spi_bitbang_stop may trigger NULL pointer dereference
> like this:
>
> BUG: KASAN: null-ptr-deref
This patch set is mainly used for reduce the overhead of switch
Intel PT configuation contex on VM-Entry/Exit by XSAVES/XRSTORS
instructions.
I measured the cycles number of context witch on Manual and
XSAVES/XRSTORES by rdtsc, and the data as below:
Manual save(rdmsr): ~334 cycles
Manual re
Introduce new fpu state structure pt_state to save Intel
processor trace configuration. The upcoming using
XSAVES/XRSTORS to switch the Intel PT configuration
on VM-Entry/Exit will use this structure.
Signed-off-by: Luwei Kang
---
arch/x86/include/asm/fpu/types.h | 13 +
1 file chang
This patch change the Intel PT configuration state
to structure pointer so that we only need to allocate
the state buffer when Intel PT working in HOST_GUEST
mode.
Signed-off-by: Luwei Kang
---
arch/x86/kvm/vmx/nested.c | 2 +-
arch/x86/kvm/vmx/vmx.c| 202 +++---
Allocate XSAVE area for host and guest Intel PT
configuration when Intel PT working in HOST_GUEST
mode. Intel PT configuration state can be saved
using XSAVES and restored by XRSTORS instruction.
Signed-off-by: Luwei Kang
---
arch/x86/kvm/vmx/vmx.c | 25 -
arch/x86/kvm/vm
This patch get the Intel PT state from xsave area to
variables when PT is change from enabled to disabled.
Because PT state is saved/restored to/from xsave area
by XSAVES/XRSTORES instructions when Intel PT is enabled.
The KVM guest may read this MSRs when PT is disabled
but the real value is saved
Remove the previous pt_ctx structure and use pt_state
to save the PT configuration because they are saved
the same things.
Add *_ctx postfix to different with the upcoming
host and guest fpu pointer for PT state.
Signed-off-by: Luwei Kang
---
arch/x86/kvm/vmx/nested.c | 2 +-
arch/x86/kvm/vmx/v
This patch add the support of using XSAVES/XRSTORS to
do the Intel processor trace context switch.
Because of native driver didn't set the XSS[bit8] to enabled
the PT state in xsave area, so this patch only set this bit
before XSAVE/XRSTORS intstuction executtion and restore the
original value aft
- Ursprüngliche Mail -
>> They are not required, but they are just useful. While you are right that the
>> locations within UBIFS are unique,
>> they are not for the whole kernel context.
>> Filesystem functions can get called via many different paths from VFS...
>
> Isn't that true for an
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-for-5.2
for you to fetch changes up to 35399f87e271f7cf3048eab00a421a6519ac
On Tue, 14 May 2019 17:12:04 +0900, Tomasz Figa wrote:
> Hi Michael,
>
> On Tue, Apr 30, 2019 at 07:34:12PM +0200, Michael Tretter wrote:
> > On Thu, 24 Jan 2019 19:04:19 +0900, Tomasz Figa wrote:
>
> [snip]
>
> > > +State machine
> > > +=
> > > +
> > > +.. kernel-render:: DOT
> >
YueHaibing 於 2019年5月16日 週四 下午3:57寫道：
>
> If spi_register_master fails in spi_bitbang_start
> because device_add failure, We should return the
> error code other than 0, otherwise calling
> spi_bitbang_stop may trigger NULL pointer dereference
> like this:
Reviewed-by: Axel Lin
On Tue, 14 May 2019 at 11:00, Anshuman Khandual
wrote:
>
> From: Mark Rutland
>
> The arm64 ptdump code can race with concurrent modification of the
> kernel page tables. At the time this was added, this was sound as:
>
> * Modifications to leaf entries could result in stale information being
>
tree->root and tree->nodes are allocated by memory allocation
functions. And tree is also an allocated memory. When allocation of
tree->root and tree->nodes fails, not freeing tree will leak memory.
Thus we should free tree in this situation.
Signed-off-by: Gen Zhang
---
diff --git a/sound/hd
On Thu, May 16, 2019 at 09:55:26AM +0800, Kefeng Wang wrote:
> Make some structs and functions static to fix build warning, parts of
> warning shown below,
>
> amples/vfio-mdev/mtty.c:730:5: warning: symbol 'mtty_create' was not
> declared. Should it be static?
> samples/vfio-mdev/mtty.c:780:5: w
On Sat, 11 May 2019 at 00:42, Doug Anderson wrote:
>
> Hi,
>
> > Use gen_rtx_set instead of gen_rtx_SET. The former is a wrapper macro
> > that handles the difference between GCC versions implementing
> > the latter.
> >
> > This fixes the following error on my system with g++ 5.4.0 as the host
>
On Thu, May 16, 2019 at 5:37 PM Michael Tretter
wrote:
>
> On Tue, 14 May 2019 17:12:04 +0900, Tomasz Figa wrote:
> > Hi Michael,
> >
> > On Tue, Apr 30, 2019 at 07:34:12PM +0200, Michael Tretter wrote:
> > > On Thu, 24 Jan 2019 19:04:19 +0900, Tomasz Figa wrote:
> >
> > [snip]
> >
> > > > +State
intel_iommu_get_resv_regions() aims to return the list of
reserved regions accessible by a given @device. However several
devices can access the same reserved memory region and when
building the list it is not safe to use a single iommu_resv_region
object, whose container is the RMRR. This iommu_re
On Thu, 16 May 2019 10:40:03 +0200,
Gen Zhang wrote:
>
> tree->root and tree->nodes are allocated by memory allocation
> functions. And tree is also an allocated memory. When allocation of
> tree->root and tree->nodes fails, not freeing tree will leak memory.
> Thus we should free tree in this
This patch adds device device tree bindings for the vibrator found on
the LG Nexus 5 (hammerhead) phone.
Signed-off-by: Brian Masney
---
This is a resend of the following patch that has missed the last two
merge windows:
https://lore.kernel.org/lkml/20190206013329.18195-4-masn...@onstation.org/
On Tue, May 14, 2019 at 10:54:45PM +0200, Jernej Skrabec wrote:
> The AP6212 is based on the Broadcom BCM43430 or BCM43438. The WiFi side
> identifies as BCM43430, while the Bluetooth side identifies as BCM43438.
>
> WiFi is connected to mmc1 and the Bluetooth side is connected to UART1
> in a 4 wi
Those helpers will access private eventpoll structure in future patches,
so keep those helpers close to callers.
Nothing important here.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
diff --git
epoll_create2() is needed to accept EPOLL_USERPOLL flags
and size, i.e. this patch wires up polling from userspace.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
diff --git a/arch/x86/entry/sysc
Not every device reports pollflags on wake_up(), expecting that it will be
polled later. vfs_poll() can't be called from ep_poll_callback(), because
ep_poll_callback() is called under the spinlock. Obviously userspace can't
call vfs_poll(), thus epoll has to offload vfs_poll() to a work and then
This one allocates user header and user events ring according to max items
number, passed as a parameter. User events (index) ring is in a pow2.
Pages, which will be shared between kernel and userspace, are accounted
through user->locked_vm counter.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
When epfd is polled by userspace and new item is inserted new bit
should be get from a bitmap and then user item is set accordingly.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
diff --git a/fs
When epfd is polled from userspace and item is being modified:
1. Update user item with new pointer or poll flags.
2. Add event to user ring if needed.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.
Rule of thumb for epfd polled from userspace is simple: epfd has
events if ->head != ->tail, no traversing of each item is performed.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
diff --git a/f
Both add and remove events are lockless and can be called in parallel.
ep_add_event_to_uring():
o user item is marked atomically as ready
o if on previous stem user item was observed as not ready,
then new entry is created for the index uring.
ep_remove_user_item():
User has to mmap user_header and user_index vmalloce'd pointers in order
to consume events from userspace. Also we do not let any copies of vma
on fork().
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kern
On ep_remove() simply mark a user item with EPOLLREMOVE if the item was
ready (i.e. has some bits set). That will prevent further user index
entry creation on item ->bit reuse.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc:
There are various of limitations if epfd is polled by user:
1. Expect always EPOLLET flag (Edge Triggered behavior)
2. No support for EPOLLWAKEUP
events are consumed from userspace, thus no way to call __pm_relax()
3. No support for EPOLLEXCLUSIVE
If device does not pass pollfla
Hi all,
This is v3 which introduces pollable epoll from userspace.
v3:
- Measurements made, represented below.
- Fix alignment for epoll_uitem structure on all 64-bit archs except
x86-64. epoll_uitem should be always 16 bit, proper BUILD_BUG_ON
is added. (Linus)
- Check pollflags expli
This one introduces structures of user items array:
struct epoll_uheader -
describes inserted epoll items.
struct epoll_uitem -
single epoll item visible to userspace.
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Al Viro
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc:
Each ep_poll_callback() is called when fd calls wakeup() on epfd.
So account new event in user ring.
The tricky part here is EPOLLONESHOT. Since we are lockless we
have to be deal with ep_poll_callbacks() called in paralle, thus
use cmpxchg to clear public event bits and filter out concurrent
cal
On Thu, May 16, 2019 at 10:49:43AM +0200, Takashi Iwai wrote:
> On Thu, 16 May 2019 10:40:03 +0200,
> Gen Zhang wrote:
> >
> > tree->root and tree->nodes are allocated by memory allocation
> > functions. And tree is also an allocated memory. When allocation of
> > tree->root and tree->nodes fail
From: Masahiro Yamada
> Sent: 15 May 2019 18:55
...
> > xargs basename -a -- | sort | ...
>
> Sorry for my ignorance, but could you
> teach me the effect of "--" ?
>
> I sometimes use "--" as a separator
> when there is ambiguity in arguments
> for example, "git log -- "
>
> In this case, w
"thread-num" is an unused property so we remove it from example.
Signed-off-by: Bibby Hsieh
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/mailbox/mtk-gce.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mailbox/mtk-gce.txt
b/Documentatio
add mt8183 compatible name for supporting gce function
Signed-off-by: Bibby Hsieh
Reviewed-by: CK Hu
---
drivers/mailbox/mtk-cmdq-mailbox.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mailbox/mtk-cmdq-mailbox.c
b/drivers/mailbox/mtk-cmdq-mailbox.c
index 87617dc7504d..6db1e2dd2d
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 +++
include/linux/mailbox/mtk-cmdq-mailbox.h | 2 +
include/linux/soc/
Client hardware would send event to GCE hardware,
mediatek,gce-event-names and mediatek,gce-events
can be used to present the event.
Signed-off-by: Bibby Hsieh
---
Documentation/devicetree/bindings/mailbox/mtk-gce.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Docu
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 +
include/linux/soc/mediatek/mtk-cmdq.h | 18 +++
1 - 100 of 888 matches
Mail list logo
