Hi Bin,
On Thu, 2019-01-10 at 08:18 -0600, Bin Liu wrote:
> Hi Min,
>
> Please briefly summarize the controller differences in the commit log,
> such as
>
> - WIC interrupt registers;
> - data toggle bit;
> - no dedicated DMA interrupt line;
>
> so that we can quickly understand the core
The perf_proc_update_handler() handles
/proc/sys/kernel/perf_event_max_sample_rate
syctl variable. When the PMU IRQ handler timing monitoring is disabled, i.e,
when /proc/sys/kernel/perf_cpu_time_max_percent is equal to 0 or 100,
then no modification to sysctl_perf_event_sample_rate is allowed
On 11/01/2019 01:47, Steven Rostedt wrote:
> On Tue, Jan 08, 2019 at 12:08:03PM +0900, Masahiro Yamada wrote:
>> ---
>>
>> drivers/vfio/pci/trace.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/vfio/pci/trace.h b/drivers/vfio/pci/trace.h
>> index
On Thu, Jan 10, 2019 at 5:59 PM Richard Guy Briggs wrote:
> On 2019-01-03 15:11, Paul Moore wrote:
> > On Wed, Oct 31, 2018 at 5:17 PM Richard Guy Briggs wrote:
> > > On 2018-10-19 19:17, Paul Moore wrote:
> > > > On Sun, Aug 5, 2018 at 4:33 AM Richard Guy Briggs
> > wrote:
> > > > > Add audit
- On Jan 10, 2019, at 12:31 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Dec 11, 2018, at 2:40 AM, Florian Weimer fwei...@redhat.com wrote:
[...]
>>
>>> diff --git a/nptl/Versions b/nptl/Versions
>>> index e7f691da7a..f7890f73fc 100644
>>> --- a/nptl/Versions
>>>
On Thu, Jan 10, 2019 at 7:13 AM joeyli wrote:
>
> On Wed, Jan 09, 2019 at 10:47:42AM -0800, Andy Lutomirski wrote:
> > On Wed, Jan 9, 2019 at 8:40 AM joeyli wrote:
> > >
> > > Hi Andy,
> > >
> > > Thanks for your review!
> > >
> > > On Tue, Jan 08, 2019 at 01:41:48PM -0800, Andy Lutomirski
On Fri, Jan 11, 2019 at 01:00:38AM +0100, Nicolai Stange wrote:
> Hi Joe,
>
> Joe Lawrence writes:
>
> > tl;dr: On ppc64le, what is top-most stack frame for scheduled tasks
> >about?
>
> If I'm reading the code in _switch() correctly, the first frame is
> completely uninitialized
On 1/10/19 12:45 PM, Song Liu wrote:
> Could you please share your feedback on PERF_RECORD_BPF_EVENT for auditing
> use cases?
Google shows Daniel was the one looking at audit use cases:
https://www.mail-archive.com/netdev@vger.kernel.org/msg250728.html
My comment was that using a
On Thu, Jan 10, 2019 at 03:32:30PM -0800, Guenter Roeck wrote:
> On Sat, Dec 08, 2018 at 12:21:38PM +0530, Chandan Rajendra wrote:
> > In order to have a common code base for fscrypt "post read" processing
> > for all filesystems which support encryption, this commit removes
> > filesystem
On January 10, 2019 9:42:57 AM PST, Sean Christopherson
wrote:
>On Thu, Jan 10, 2019 at 12:32:43PM -0500, Steven Rostedt wrote:
>> On Thu, 10 Jan 2019 11:20:04 -0600
>> Josh Poimboeuf wrote:
>>
>>
>> > > While I can't find a reason for hypervisors to emulate this
>instruction,
>> > > smarter
On 1/10/19 3:31 PM, Andrew Morton wrote:
On Fri, 4 Jan 2019 03:27:52 +0800 Yang Shi wrote:
Swap readahead would read in a few pages regardless if the underlying
device is busy or not. It may incur long waiting time if the device is
congested, and it may also exacerbate the congestion.
> -Original Message-
> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
> Sent: Friday, December 21, 2018 6:00 PM
> To: Jiaying Liang
> Cc: Michal Simek ; Rob Herring ;
> Mark Rutland ; Linux Kernel Mailing List ker...@vger.kernel.org>; linux-arm-ker...@lists.infradead.org;
On Thu, Jan 10, 2019 at 3:02 PM Linus Torvalds
wrote:
>
> On Thu, Jan 10, 2019 at 12:52 PM Josh Poimboeuf wrote:
> >
> > Right, emulating a call instruction from the #BP handler is ugly,
> > because you have to somehow grow the stack to make room for the return
> > address. Personally I liked
Jerome Brunet writes:
> On platforms making a fair use of regulators, the dev_info() messages
> coming from the device link function are a bit too verbose. The amount
> of message will increase further with the clock framework joining the
> device link party.
>
> These messages looks valuable
On Thu, Jan 10, 2019 at 08:18:37PM +0530, Balakrishna Godavarthi wrote:
> Hi Johan,
>
> On 2019-01-09 20:08, Johan Hovold wrote:
> > On Fri, Dec 21, 2018 at 05:59:47PM -0800, Matthias Kaehlcke wrote:
> > > On Thu, Dec 20, 2018 at 08:16:35PM +0530, Balakrishna Godavarthi
> > > wrote:
> > > >
Jerome Brunet writes:
> On Sat, 2018-12-22 at 18:01 +0100, Martin Blumenstingl wrote:
>> Hi Jerome,
>>
>> On Thu, Dec 20, 2018 at 5:11 PM Jerome Brunet wrote:
>> > While some 3.3v eMMC 4.0 are available from libretech, the default
>> > option for the aml-s905x-cc seems to 1.8v 5.0 modules.
>>
On Thu, 10 Jan 2019 12:10:34 -0500
Steven Rostedt wrote:
> On Thu, 10 Jan 2019 23:57:10 +0900
> Masami Hiramatsu wrote:
>
> > > Same for all patches in this series...
> >
> > Oops, sorry. I'll fix the format again.
> > BTW, I'm still considering I should make it other patches in this series
Hi Jon
> Actually no. Looking at snd_soc_init_multicodec() it always allocates
> memory if any of the 'legacy' codec members
> (codec_name/codec_of_node/codec_dai_name) are populated. However, this
> looks quite fragile to me and is susceptible to leaking memory if the
> user/machine driver
Hi Andrea,
On Thu, 10 Jan 2019 18:39:47 +0100
Andrea Righi wrote:
> It is possible to trigger a NULL pointer dereference by writing an
> incorrectly formatted string to krpobe_events (omitting the symbol).
>
> Example:
>
> echo "r:event_1 " >> /sys/kernel/debug/tracing/kprobe_events
>
>
On Thu, Jan 10, 2019 at 3:07 PM Kees Cook wrote:
>
> On Thu, Jan 10, 2019 at 1:10 PM Khalid Aziz wrote:
> > I implemented a solution to reduce performance penalty and
> > that has had large impact. When XPFO code flushes stale TLB entries,
> > it does so for all CPUs on the system which may
From: George Hilliard
These drivers are useful on other MT76xx SoCs, which have compatible
peripherals. The drivers are selectable in Kconfig, but they were
quietly excluded from the build because the SOC_MT7621 chip was not
selected. So, make the main staging Makefile use the same flags as
From: George Hilliard
This is in preparation to allow it and the mt7621-dma drivers to be
built separately. They are completely independent pieces of software,
and the Kconfig specifies very different requirements.
Cc: linux-kernel@vger.kernel.org
Cc: de...@driverdev.osuosl.org
Cc: Neil Brown
Jerome Brunet writes:
> This patchset adds spdif input support to the axg SoC family and the
> s400 reference design.
>
> Kevin, ASoC support for this spdif input (including the binding doc) just
> got merged in the ASoC tree [0]. Until the related patches hit mainline,
> you may get a warning
Neil Armstrong writes:
> On 08/12/2018 18:12, Martin Blumenstingl wrote:
>> This series adds support for the Mali-450 GPU on Meson8 and Meson8b.
>> Meson6 uses a Mali-400 GPU but since we don't have a clock driver (and
>> I don't have a device for testing) Meson6 is left out in this series.
>>
Neil Armstrong writes:
> On 08/12/2018 17:50, Martin Blumenstingl wrote:
>> This adds the APB bus on Meson8 and Meson8b as well as the APB2 bus on
>> Meson6. This is preparation work for adding the Mali GPU which is
>> located on theses busses.
>>
>> Meson6 seems to have it's APB at 0xc800
>> +static int sdhci_tegra_add_host(struct sdhci_host *host) {
>> +struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host);
>> +struct sdhci_tegra *tegra_host = sdhci_pltfm_priv(pltfm_host);
>> +struct cqhci_host *cq_host;
>> +bool dma64;
>> +int ret;
>> +
>> +if
On Thu, Jan 10, 2019 at 05:30:56AM +0530, Amit Kucheria wrote:
> Since the big and little cpus are in the same frequency domain, use all
> of them for mitigation in the cooling-map. At the lower trip points we
> restrict ourselves to throttling only a few OPPs. At higher trip
> temperatures, allow
On Thu, Jan 10, 2019 at 3:54 PM Sean Christopherson
wrote:
>
> On Thu, Jan 10, 2019 at 01:34:44PM -0800, Andy Lutomirski wrote:
> > >> On Jan 9, 2019, at 8:31 AM, Sean Christopherson
> > >> wrote:
> > >>
> > >> On Tue, Jan 08, 2019 at 02:54:11PM -0800, Andy Lutomirski wrote:
> > >
> > >> I do
Cc: Alexander Viro
Cc: Peter Zijlstra (Intel)
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Link: http://lkml.kernel.org/g/20150807115710.ga16...@redhat.com
Acked-by: Oleg Nesterov
Signed-off-by: Vineet Gupta
---
fs/exec.c | 7 +--
1 file changed, 1 insertion(+), 6
Hi,
I did these a while back and forget. Rebased to 5.0-rc1.
Please consider applying.
Thx,
-Vineet
Vineet Gupta (3):
coredump: Replace opencoded set_mask_bits()
fs: inode_set_flags() replace opencoded set_mask_bits()
bitops.h: set_mask_bits() to return old value
fs/exec.c
It seems that 5f16f3225b0624 and 00a1a053ebe5, both with same commitlog
("ext4: atomically set inode->i_flags in ext4_set_inode_flags()")
introduced the set_mask_bits API, but somehow missed not using it in
ext4 in the end
Also, set_mask_bits is used in fs quite a bit and we can possibly come up
| > Also, set_mask_bits is used in fs quite a bit and we can possibly come up
| > with a generic llsc based implementation (w/o the cmpxchg loop)
|
| May I also suggest changing the return value of set_mask_bits() to old.
|
| You can compute the new value given old, but you cannot compute the old
On 01/08/2019 05:39 PM, Michal Hocko wrote:
On Tue 08-01-19 16:35:42, kbuild test robot wrote:
[...]
All warnings (new ones prefixed by >>):
include/linux/rcupdate.h:659:9: warning: context imbalance in
'find_lock_task_mm' - wrong count at exit
include/linux/sched/mm.h:141:37:
Thanks for looking this over.
On 1/10/19 4:07 PM, Kees Cook wrote:
> On Thu, Jan 10, 2019 at 1:10 PM Khalid Aziz wrote:
>> I implemented a solution to reduce performance penalty and
>> that has had large impact. When XPFO code flushes stale TLB entries,
>> it does so for all CPUs on the system
sync changes for PERF_RECORD_KSYMBOL
Signed-off-by: Song Liu
---
tools/include/uapi/linux/perf_event.h | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index
This patch handles PERF_RECORD_KSYMBOL in perf record/report.
Specifically, map and symbol are created for ksymbol register, and
removed for ksymbol unregister.
This patch also set perf_event_attr.ksymbol properly. The flag is
ON by default.
Signed-off-by: Song Liu
---
tools/perf/util/event.c
This set catches symbol for all bpf programs loaded/unloaded
before/during/after perf-record run PERF_RECORD_KSYMBOL and
PERF_RECORD_BPF_EVENT.
PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT includes key information
of a bpf program load and unload. They are sent through perf ringbuffer,
and
Hi Andy,
On Mon, Dec 10, 2018 at 11:28 AM Evan Green wrote:
>
> Add the UFS controller and PHY to SDM845.
>
> Signed-off-by: Evan Green
> Signed-off-by: Douglas Anderson
> Reviewed-by: Bjorn Andersson
>
> ---
> As Doug mentioned in v2, this should land after (or with) the driver fix
> in this
For better performance analysis of dynamically JITed and loaded kernel
functions, such as BPF programs, this patch introduces
PERF_RECORD_KSYMBOL, a new perf_event_type that exposes kernel symbol
register/unregister information to user space.
The following data structure is used for
This patch adds basic handling of PERF_RECORD_BPF_EVENT.
Tracking of PERF_RECORD_BPF_EVENT is OFF by default. Option --bpf-event
is added to turn it on.
Signed-off-by: Song Liu
---
tools/perf/builtin-record.c | 1 +
tools/perf/perf.h | 1 +
tools/perf/util/Build | 2 ++
For better performance analysis of BPF programs, this patch introduces
PERF_RECORD_BPF_EVENT, a new perf_event_type that exposes BPF program
load/unload information to user space.
Each BPF program may contain up to BPF_MAX_SUBPROGS (256) sub programs.
The following example shows kernel symbols
sync for PERF_RECORD_BPF_EVENT
Signed-off-by: Song Liu
---
tools/include/uapi/linux/perf_event.h | 29 ++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index
This patch enables emitting PERF_RECORD_KSYMBOL for BPF program load and
unload. A PERF_RECORD_KSYMBOL is issued for each BPF sub program.
Signed-off-by: Song Liu
---
kernel/events/core.c | 34 ++
1 file changed, 34 insertions(+)
diff --git
This patch synthesize PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT for
BPF programs loaded before perf-record. This is achieved by gathering
information about all BPF programs via sys_bpf.
Signed-off-by: Song Liu
---
tools/perf/builtin-record.c | 6 ++
tools/perf/util/bpf-event.c | 205
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/omapdrm/omap_encoder.c
between commit:
3c613a3bddd3 ("drm/omap: fix incorrect union usage")
from Linus' tree and commit:
13d0add333af ("drm/edid: Pass connector to AVI infoframe functions")
from
Jerome Brunet writes:
> On Wed, 2018-09-12 at 21:49 -0700, Kevin Hilman wrote:
>> Jerome Brunet writes:
>>
>> > Compile the necessary drivers as modules, including codecs, for the
>> > s400 sound card.
>> >
>> > Signed-off-by: Jerome Brunet
>>
>> Applied to v4.20/defconfig.
>
> Hi Kevin,
>
On Fri, 11 Jan 2019 00:56:42 +0100
Christian Brauner wrote:
> > - Please consider doing this in RST and tying it into our documentation
> >tree. It's *almost* RST now, so the effort required will be almost
> >zero.
>
> Oh sure. I simply didn't know. I was just going by the files
Using SPDX commenting style // or /* is specified for
various file types in Documentation/process/license-rules.rst
so add an appropriate test for .[chsS] files because many
proposed file additions and patches do not use the correct style.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl |
James,
> Q1 - I'm hoping you can clarify how this should be interpreted.
>
> I originally took this to mean the number of bytes into the first
> discard_granularity block that the partition resides at. i.e. If
> discard_granularity_block is 128MB, and partition 1 starts at sector
> 2048 with
Hi Joe,
Joe Lawrence writes:
> tl;dr: On ppc64le, what is top-most stack frame for scheduled tasks
>about?
If I'm reading the code in _switch() correctly, the first frame is
completely uninitialized except for the pointer back to the caller's
stack frame.
For completeness: _switch()
Michal Hocko wrote:
> On Wed 09-01-19 20:34:46, Tetsuo Handa wrote:
> > On 2019/01/09 20:03, Michal Hocko wrote:
> > > Tetsuo,
> > > can you confirm that these two patches are fixing the issue you have
> > > reported please?
> > >
> >
> > My patch fixes the issue better than your "[PATCH 2/2]
On Wed, Jan 02, 2019 at 07:14:31PM -0800, Shakeel Butt wrote:
> The [ip,ip6,arp]_tables use x_tables_info internally and the underlying
> memory is already accounted to kmemcg. Do the same for ebtables. The
> syzbot, by using setsockopt(EBT_SO_SET_ENTRIES), was able to OOM the
> whole system from
On Thu, Jan 10, 2019 at 04:47:03PM -0700, Jonathan Corbet wrote:
> On Fri, 11 Jan 2019 00:13:09 +0100
> Christian Brauner wrote:
>
> > This documents the Android binderfs filesystem used to dynamically add and
> > remove binder devices that are private to each instance.
> >
> > Signed-off-by:
h/sh/include/generated/asm/syscall_table.h'. Stop.
This affects all 'sh' builds. Not surprisingly, reverting the patch fixes
the problem.
Guenter
---
# bad: [6cab33afc3dd17bd9922c99a828f5680b4667cd9] Add linux-next specific files
for 20190110
# good: [bfeffd155283772bbe78c6a05dec7c0128ee500c] Linux
On Thu, Jan 10, 2019 at 01:34:44PM -0800, Andy Lutomirski wrote:
> >> On Jan 9, 2019, at 8:31 AM, Sean Christopherson
> >> wrote:
> >>
> >> On Tue, Jan 08, 2019 at 02:54:11PM -0800, Andy Lutomirski wrote:
> >
> >> I do think it makes sense to have QEMU delegate the various ENCLS
> >> operations
Jacek
On 1/10/19 4:03 PM, Jacek Anaszewski wrote:
> On 1/10/19 9:43 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 1/10/19 1:57 PM, Jacek Anaszewski wrote:
>>> Dan,
>>>
>>> On 1/10/19 8:22 PM, Dan Murphy wrote:
Jacek
On 1/10/19 12:44 PM, Jacek Anaszewski wrote:
> Hi Dan,
>
>
On Thu, 10 Jan 2019 14:13:44 +0100 peter enderborg
wrote:
> On 1/7/19 11:56 PM, Andrew Morton wrote:
> > On Sat, 5 Jan 2019 13:35:33 -0800 Linus Torvalds
> > wrote:
> >
> >> On Sat, Jan 5, 2019 at 1:21 PM Olof Johansson wrote:
> >>> Fixes build break on most ARM/ARM64 defconfigs:
> >>
There has been some confusion since checkpatch started warning about bool
use in structures, and people have been avoiding using it.
Many people feel there is still a legitimate place for bool in structures,
so provide some guidance on bool usage derived from the entire thread that
spawned the
On Fri, 11 Jan 2019 00:13:09 +0100
Christian Brauner wrote:
> This documents the Android binderfs filesystem used to dynamically add and
> remove binder devices that are private to each instance.
>
> Signed-off-by: Christian Brauner
Seems like a worthwhile addition overall. I know nothing
On Fri, Jan 04, 2019 at 03:35:31PM -0700, Jason Gunthorpe wrote:
> Commit 2db76d7c3c6d ("lib/scatterlist: sg_page_iter: support sg lists w/o
> backing pages") introduced the sg_page_iter_dma_address() function without
> providing a way to use it in the general case. If the sg_dma_len is not
>
> >
> > + if (si->flags & (SWP_BLKDEV | SWP_FS)) {
>
> I re-read your discussion with Tim and I must say the reasoning behind this
> test remain foggy.
I was worried that the dereference
inode = si->swap_file->f_mapping->host;
is not always safe for corner cases.
So the test makes sure that
First of all, thanks for picking this back up. It looks to be going in
a very positive direction!
On 1/10/19 1:09 PM, Khalid Aziz wrote:
> I implemented a solution to reduce performance penalty and
> that has had large impact. When XPFO code flushes stale TLB entries,
> it does so for all CPUs
On Thu, 10 Jan 2019 09:52:00 -0800 Andrei Vagin wrote:
> Currently, exit_ptrace() adds all ptraced tasks in a dead list, than
> zap_pid_ns_processes() waits all tasks in a current pidns, and only
> then tasks from the dead list are released.
>
> zap_pid_ns_processes() can stuck on waiting tasks
None of synchronize_rcu_bh, synchronize_rcu_bh_expedited, call_rcu_bh,
rcu_barrier_bh, synchronize_sched, synchronize_sched_expedited,
call_rcu_sched, rcu_barrier_sched, get_state_synchronize_sched, and
cond_synchronize_sched are actually used. This commit therefore removes
their trivial
Hi,
On Thu, Jan 10, 2019 at 03:01:14PM -0800, Eric Biggers wrote:
> On Fri, Jan 11, 2019 at 12:29:28AM +0200, Aaro Koskinen wrote:
> > Hi,
> >
> > On Fri, Jan 04, 2019 at 05:28:02PM +, David Howells wrote:
> > > Eric Biggers wrote:
> > > > Hi Aaro, thanks for the bug report! I think you're
tion "Kconfig recursive dependency limitations"
Didn't we have exactly the same problem before ?
Guenter
---
# bad: [6cab33afc3dd17bd9922c99a828f5680b4667cd9] Add linux-next specific files
for 20190110
# good: [bfeffd155283772bbe78c6a05dec7c0128ee500c] Linux 5.0-
On Fri, 4 Jan 2019 03:27:52 +0800 Yang Shi wrote:
> Swap readahead would read in a few pages regardless if the underlying
> device is busy or not. It may incur long waiting time if the device is
> congested, and it may also exacerbate the congestion.
>
> Use inode_read_congested() to check if
It doesn't make sense to call the header binder_ctl.h when its sole
existence is tied to binderfs. So give it a sensible name. Users will far
more easily remember binderfs.h than binder_ctl.h.
Signed-off-by: Christian Brauner
---
drivers/android/binderfs.c | 2 +-
On Fri, 4 Jan 2019 03:27:52 +0800 Yang Shi wrote:
> Swap readahead would read in a few pages regardless if the underlying
> device is busy or not. It may incur long waiting time if the device is
> congested, and it may also exacerbate the congestion.
>
> Use inode_read_congested() to check if
> > I'm not all that exited about spreading version requirements in the
> > source: we report this requirement in our README, and apparently we
> > already struggle to keep this information up-to-date. So what about
> > squashing something like the below (assume that 7.52 will be released
> > by
Hello Dear
Am a dying woman here in the hospital, i was diagnose as a cancer patient years
ago. I am from (Zarqa) Jordan, a business woman dealing with Gold Exportation.
I have a charitable and unfufilment project that am about to handover to you,
hope to hear from you.
Regard
Mrs Mimi
On Thu, 2019-01-10 at 14:49 -0800, Vadim Bendebury wrote:
> Presently C99 style comments are removed unconditionally before actual
> patch validity check happens. This is a problem for some third party
> projects which use checkpatch.pl but do not allow C99 style comments.
>
> This patch adds yet
On Tue, Jan 08, 2019 at 01:59:10PM -0800, Sowjanya Komatineni wrote:
> Tegra194 supports maximum 64K Bytes transfer per packet.
> Tegra186 and prior supports maximum 4K Bytes transfer per packet.
>
> This patch fixes this payload difference between Tegra194 and prior
> tegra chipsets using
Hi Stephen,
> Hi all,
>
> On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
>
> Actually this is only treated as a warning.
Thanks for the notification. I will look on
On Thu, Jan 10, 2019 at 11:42:32PM +0100, Arnd Bergmann wrote:
> On Thu, Jan 10, 2019 at 7:10 PM Joseph Myers wrote:
> >
> > On Thu, 10 Jan 2019, Arnd Bergmann wrote:
> >
> > > - Add system calls that have not yet been integrated into all
> > > architectures but that we definitely want there.
>
This documents the Android binderfs filesystem used to dynamically add and
remove binder devices that are private to each instance.
Signed-off-by: Christian Brauner
---
Documentation/filesystems/binderfs.txt | 109 +
1 file changed, 109 insertions(+)
create mode 100644
On Wed, Jan 09, 2019 at 03:33:07PM +0800, Yi Zeng wrote:
> If set adapter->retries to minus value from user space via ioctl,
> will make __i2c_transfer and __i2c_smbus_xfer jump the calling to
> adapter->algo->master_xfer and adapter->algo->smbus_xfer that
> registered by the underlying bus
_HPX Type 3 is intended to be more generic and allow configuration of
settings not possible with Type 2 tables. For example, FW could ensure
that the completion timeout value is set accordingly throughout the PCI
tree; some switches require very special handling.
Type 3 can come in an arbitrary
On Thu, Jan 10, 2019 at 12:52 PM Josh Poimboeuf wrote:
>
> Right, emulating a call instruction from the #BP handler is ugly,
> because you have to somehow grow the stack to make room for the return
> address. Personally I liked the idea of shifting the iret frame by 16
> bytes in the #DB entry
On 1/10/19 12:17 PM, Boris Ostrovsky wrote:
> On 1/10/19 11:14 AM, Juergen Gross wrote:
>> On 10/01/2019 16:34, Boris Ostrovsky wrote:
>>> On 1/10/19 5:07 AM, Juergen Gross wrote:
+void xen_clocksource_suspend(void)
+{
+ xen_clock_value_saved = xen_clocksource_read() -
On Thu, Jan 10, 2019 at 1:10 PM Khalid Aziz wrote:
> I implemented a solution to reduce performance penalty and
> that has had large impact. When XPFO code flushes stale TLB entries,
> it does so for all CPUs on the system which may include CPUs that
> may not have any matching TLB entries or may
Because the irq was requested through device managed resources API
(devm_request_threaded_irq()) it was freed after meson_mmc_remove()
completion, thus after mmc_free_host() has reclaimed meson_host memory.
As this irq is IRQF_SHARED, while using CONFIG_DEBUG_SHIRQ, its handler
get called by
The Altera Freeze Bridge should not be restricted to ARCH_SOCFPGA
since it can be used on other platforms such as Stratix10.
Signed-off-by: Alan Tull
---
drivers/fpga/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
index
Hey all,
Frequently, since support for the HiKey960's UFS code landed in
4.19, I've noticed the following warning on reboot:
[ 23.086860] WARNING: CPU: 0 PID: 2507 at
drivers/scsi/ufs/ufshcd.c:2460 ufshcd_queuecommand+0x59c/0x5a8
[ 23.096256] Modules linked in:
[ 23.099313] CPU: 0 PID:
On Fri, Jan 11, 2019 at 12:29:28AM +0200, Aaro Koskinen wrote:
> Hi,
>
> On Fri, Jan 04, 2019 at 05:28:02PM +, David Howells wrote:
> > Eric Biggers wrote:
> > > Hi Aaro, thanks for the bug report! I think you're on the right track;
> > > it makes
> > > much more sense to have the keyrings
>> @@ -636,6 +649,9 @@ static irqreturn_t tegra_i2c_isr(int irq, void *dev_id)
>> goto err;
>> }
>>
>> +if (i2c_dev->hw->has_bus_clr_support && (status & I2C_INT_BUS_CLR_DONE))
>> +goto err;
>> +
>
>This looks odd. If we support bus clear and the BUS_CLR_DONE
On 2019-01-03 15:11, Paul Moore wrote:
> On Wed, Oct 31, 2018 at 5:17 PM Richard Guy Briggs wrote:
> > On 2018-10-19 19:17, Paul Moore wrote:
> > > On Sun, Aug 5, 2018 at 4:33 AM Richard Guy Briggs
> wrote:
> > > > Add audit container identifier auxiliary record to tty logging rule
> > > > event
The console debug/stacks/info from just now. The previous config, current
kernel from github.
--
Esme
[ 75.783231] kasan: CONFIG_KASAN_INLINE enabled
[ 75.785870] kasan: GPF could be caused by NULL-ptr deref or user memory
access
[ 75.787695] general protection fault: [#1] SMP KASAN
Am Mittwoch, 5. Dezember 2018, 13:33:10 CET schrieb Helen Koike:
> From: Enric Balletbo i Serra
>
> Add support to async updates of cursors by using the new atomic
> interface for that.
>
> Signed-off-by: Enric Balletbo i Serra
> [updated for upstream]
> Signed-off-by: Helen Koike
applied to
Hi all,
On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
wrote:
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
Actually this is only treated as a warning.
> arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning (spi_bus_bridge):
>
Greg Kroah-Hartman wrote...
> Ok, Breno and Christoph, what should I do here? Should I drop this
> patch in the tree or add this new one? Ideally I can fix this soon as I
> don't like having broken trees out there...
Whatever Breno says - I don't feel competent enough to decide what's
right
On Wed, Jan 09, 2019 at 02:11:25PM +0530, Aneesh Kumar K.V wrote:
> Andrew Morton writes:
>
> > On Tue, 8 Jan 2019 10:21:06 +0530 "Aneesh Kumar K.V"
> > wrote:
> >
> >> ppc64 use CMA area for the allocation of guest page table (hash page
> >> table). We won't
> >> be able to start guest if
On Thu, Jan 10, 2019 at 07:49:08PM +0100, Remi Pommarel wrote:
> Because the irq was requested through device managed resources API
> (devm_request_threaded_irq()) it was freed after meson_mmc_remove()
> completion, thus after mmc_free_host() has reclaimed meson_host memory.
> As this irq is
On Thu, Jan 10, 2019 at 1:29 PM Dan Williams wrote:
> Note that higher order merging is not a current concern since the
> implementation is already randomizing on MAX_ORDER sized pages. Since
> memory side caches are so large there's no worry about a 4MB
> randomization boundary.
>
> However, for
On Wed, Jan 9, 2019 at 11:01 PM Greg KH wrote:
>
> On Wed, Jan 09, 2019 at 04:19:30PM -0800, Nick Desaulniers wrote:
> > Digging up an old thread to point out I was wrong:
> >
> > On Thu, Sep 27, 2018 at 1:08 PM Nick Desaulniers
> > wrote:
> > > > This is not a million-little-commits problem;
Presently C99 style comments are removed unconditionally before actual
patch validity check happens. This is a problem for some third party
projects which use checkpatch.pl but do not allow C99 style comments.
This patch adds yet another variable, named C99_COMMENT_TOLERANCE. If
it is included in
On Thu, Jan 10, 2019 at 08:31:26AM -0800, Paul E. McKenney wrote:
> On Thu, Jan 10, 2019 at 10:41:23AM -0500, Alan Stern wrote:
> > On Thu, 10 Jan 2019, Paul E. McKenney wrote:
> >
> > > On Thu, Jan 10, 2019 at 09:40:24AM +0100, Andrea Parri wrote:
> > > > > > > > It seems that
> > > > > > > >
>
Add pinctrls for 3V3 and 1V8 pad drive strength configuration for
Tegra210 sdmmc.
Tegra210 sdmmc has pad configuration registers in pinmux register
domain and handled thru pinctrl to pinmux device node.
Tegra186 and Tegra194 has pad configuration register with in the
SDMMC register domain itself
Add SDMMC initial pad offsets used by auto calibration process.
Add SDMMC fixed drive strengths for Tegra210, Tegra186 and
Tegra194 which are used when calibration timeouts.
Fixed drive strengths are based on Pre SI Analysis of the pads.
Signed-off-by: Sowjanya Komatineni
---
Program initial drive code offsets which will be used by auto
calibration process.
Program fixed drive strengths for SDMMC pads in pad control
register when auto cal timeouts.
Fixed settings are based on Pre-SI analysis of the pad design.
Signed-off-by: Sowjanya Komatineni
---
201 - 300 of 1151 matches
Mail list logo
