On Fri, May 1, 2020 at 2:27 AM Shakeel Butt wrote:
>
> Lowering memory.max can trigger an oom-kill if the reclaim does not
> succeed. However if oom-killer does not find a process for killing, it
> dumps a lot of warnings.
>
I have been confused by this behavior for several months and I think
it
This reverts commit 580d952e44de5509c69c8f9346180ecaa78ebeec ("tty:
serial: bcm63xx: fix missing clk_put() in bcm63xx_uart") because we
should not be doing a clk_put() if we were not successful in getting a
valid clock reference via clk_get() in the first place.
Fixes: 580d952e44de ("tty: serial:
his patchset tries to ensure that VT is preferred in those conditions
> even in the presence of firmware-mandated serial consoles. These should
> cleanly apply onto next-20200430.
Well, if there is a "mandated console", then why would we prefer
any other console?
-ss
On Thu, Apr 30, 2020 at 06:18:18PM -0700, Joe Perches wrote:
> On Thu, 2020-04-30 at 18:13 -0700, Guru Das Srinagesh wrote:
> > On Wed, Apr 29, 2020 at 08:50:10AM +0100, Lee Jones wrote:
> > > On Tue, 28 Apr 2020, Guru Das Srinagesh wrote:
> > > > The Qualcomm Technologies, Inc. I2C PMIC
On Thu, Apr 30, 2020 at 5:10 PM Linus Torvalds
wrote:
>
> On Thu, Apr 30, 2020 at 4:52 PM Dan Williams wrote:
> >
> > You had me until here. Up to this point I was grokking that Andy's
> > "_fallible" suggestion does help explain better than "_safe", because
> > the copy is doing extra safety
On 4/30/2020 4:26 PM, Doug Berger wrote:
> The side band interrupt service routine is not available on chips
> like 7211, or rather, it does not permit the signaling of wake-up
> events due to the complex interrupt hierarchy.
>
> Move the wake-up event accounting into a .resume_noirq function,
> On Apr 30, 2020, at 5:25 PM, Linus Torvalds
> wrote:
>
>
> It wasn't clear how "copy_to_mc()" could ever fault. Poisoning
> after-the-fact? Why would that be preferable to just mapping a dummy
> page?
If the kernel gets an async memory error and maps a dummy page, then subsequent
reads
On 2020-05-01 04:32, Bart Van Assche wrote:
On 2020-04-29 22:40, Can Guo wrote:
On 2020-04-30 13:08, Bart Van Assche wrote:
On 2020-04-29 21:10, Can Guo wrote:
During system resume, scsi_resume_device() decreases a request
queue's
pm_only counter if the scsi device was quiesced before. But
On Thu, 2020-04-30 at 18:13 -0700, Guru Das Srinagesh wrote:
> On Wed, Apr 29, 2020 at 08:50:10AM +0100, Lee Jones wrote:
> > On Tue, 28 Apr 2020, Guru Das Srinagesh wrote:
> > > The Qualcomm Technologies, Inc. I2C PMIC Controller is used by
> > > multi-function PMIC devices which communicate over
This patch is to let ethtool enable/disable the tc flower offload
features. Hardware ENETC has the feature of PSFP which is for per-stream
policing. When enable the tc hw offloading feature, driver would enable
the IEEE 802.1Qci feature. It is only set the register enable bit for
this feature not
Changes from V4:
0001:
Fix and modify according to Vlid Buslov suggestions:
- Change spin_lock_bh() to spin_lock() since tcf_gate_act() already in
software irq.
- Remove spin lock protect in the ops->cleanup function.
- Enable the CONFIG_DEBUG_ATOMIC_SLEEP and CONFIG_PROVE_LOCKING
Introduce a ingress frame gate control flow action.
Tc gate action does the work like this:
Assume there is a gate allow specified ingress frames can be passed at
specific time slot, and be dropped at specific time slot. Tc filter
chooses the ingress frames, and tc gate action would specify what
Add the gate action to the flow action entry. Add the gate parameters to
the tc_setup_flow_action() queueing to the entries of flow_action_entry
array provide to the driver.
Signed-off-by: Po Liu
---
include/net/flow_offload.h | 10
include/net/tc_act/tc_gate.h | 99
This patch is to add tc flower offload for the enetc IEEE 802.1Qci(PSFP)
function. There are four main feature parts to implement the flow
policing and filtering for ingress flow with IEEE 802.1Qci features.
They are stream identify(this is defined in the P802.1cb exactly but
needed for 802.1Qci),
On Wed, Apr 29, 2020 at 08:50:10AM +0100, Lee Jones wrote:
> On Tue, 28 Apr 2020, Guru Das Srinagesh wrote:
>
> > The Qualcomm Technologies, Inc. I2C PMIC Controller is used by
> > multi-function PMIC devices which communicate over the I2C bus. The
> > controller enumerates all child nodes as
[ Joerg, sending again this time not just to you. (hit reply to sender
and not reply to all). Feel free to resend what you wrote before to this ]
On Thu, 30 Apr 2020 21:14:34 +0200
Joerg Roedel wrote:
> And alloc_percpu() calls down into pcpu_alloc(), which allocates new
> percpu chunks
On Thu, 30 Apr 2020, Yang Shi wrote:
> On 4/30/20 2:59 PM, Kirill A. Shutemov wrote:
> > On Thu, Apr 30, 2020 at 06:56:21AM +0800, Yang Shi wrote:
> > > The max_ptes_{swap|none|shared} are defined to tune the behavior of
> > > khugepaged. The are checked at a couple of places with open coding.
>
> On Apr 30, 2020, at 5:40 PM, Linus Torvalds
> wrote:
>
> On Thu, Apr 30, 2020 at 5:23 PM Andy Lutomirski wrote:
>>
>>> But anyway, I don't hate something like "copy_to_user_fallible()"
>>> conceptually. The naming needs to be fixed, in that "user" can always
>>> take a fault, so it's
On Thu, Apr 30, 2020 at 04:11:18PM -0400, Daniel Jordan wrote:
> Sometimes the kernel doesn't take full advantage of system memory
> bandwidth, leading to a single CPU spending excessive time in
> initialization paths where the data scales with memory size.
>
> Multithreading naturally addresses
On Thu, Apr 30, 2020 at 04:05:07PM +0200, Arnd Bergmann wrote:
> lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x133: call to
> do_strncpy_from_user() with UACCESS enabled
> lib/strnlen_user.o: warning: objtool: strnlen_user()+0x122: call to
> do_strnlen_user() with UACCESS
Hi all,
On Fri, 1 May 2020 10:24:53 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the btrfs tree got a conflict in:
>
> fs/btrfs/transaction.c
>
> between commit:
>
> fcc99734d1d4 ("btrfs: transaction: Avoid deadlock due to bad initialization
> timing of
From: Alex Elder
Date: Thu, 30 Apr 2020 16:35:09 -0500
> This series fixes three bugs in the Qualcomm IPA code. The third
> adds a missing error code initialization step.
Series applied, thanks.
On Mon, Apr 27, 2020 at 09:22:33AM +0200, Thierry Reding wrote:
On Fri, Apr 24, 2020 at 08:22:28AM -0400, Sasha Levin wrote:
From: Dmitry Osipenko
[ Upstream commit a900aeac253729411cf33c6cb598c152e9e4137f ]
Boot CPU0 always handle I2C interrupt and under some rare circumstances
(like
On Fri, Apr 24, 2020 at 02:45:55PM +0200, Takashi Iwai wrote:
On Fri, 24 Apr 2020 14:24:36 +0200,
Sasha Levin wrote:
From: Takashi Iwai
[ Upstream commit 9479e75fca370a5220784f7596bf598c4dad0b9b ]
Currently, when the HD-audio controller driver doesn't detect any
codecs, it tries to abort
Hi Daniil,
On Fri, May 01, 2020 at 10:15:18AM +1000, Daniil Lunev wrote:
> On the official revision of coreboot for hatch it doesn't even try to
> load Type C. However it gives some warning messages from
> cros-usbpd-notify-acpi about EC, So I wonder why the check of the same
> type is not
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c45e8bccecaf633480d378daff11e122dfd5e96d
commit: 07b586fe06625b0b610dc3d3a969c51913d143d4 crypto: x86/curve25519 -
replace with formally verified implementation
date: 3 months ago
config:
On Thu, Apr 30, 2020 at 02:31:31PM -0700, Andrew Morton wrote:
> On Thu, 30 Apr 2020 16:11:18 -0400 Daniel Jordan
> wrote:
> > Sometimes the kernel doesn't take full advantage of system memory
> > bandwidth, leading to a single CPU spending excessive time in
> > initialization paths where the
From: Julia Lawall
Date: Thu, 30 Apr 2020 21:51:32 +0200
> In this code, it appears that phyter_clocks is a list head, based on
> the previous list_for_each, and that clock->list is intended to be a
> list element, given that it has just been initialized in
> dp83640_clock_init. Accordingly,
Commit 1c30844d2dfe ("mm: reclaim small amounts of memory when an external
fragmentation event occurs") adds a boost_watermark() function which
increases the min watermark in a zone by at least pageblock_nr_pages or
the number of pages in a page block. On Arm64, with 64K pages and 512M
huge pages,
On Thu, Apr 30, 2020 at 5:23 PM Andy Lutomirski wrote:
>
> > But anyway, I don't hate something like "copy_to_user_fallible()"
> > conceptually. The naming needs to be fixed, in that "user" can always
> > take a fault, so it's the _source_ that can fault, not the "user"
> > part.
>
> I don’t like
Hi Bjorn,
On 4/30/2020 3:40 PM, Bjorn Helgaas wrote:
[+cc Austin, Mario, Jon, Alex, Rafael, Keith, Sinan, Tyler]
On Sun, Apr 26, 2020 at 11:30:06AM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
From: Kuppuswamy Sathyanarayanan
Currently PCIe AER driver uses HEST FIRMWARE_FIRST
On Thu, Apr 30, 2020 at 04:05:07PM +0200, Arnd Bergmann wrote:
> lib/locking-selftest.o: warning: objtool: locking_selftest()+0x117f: PUSHF
> stack exhausted
> lib/locking-selftest.o: warning: objtool: ww_tests()+0x1083: PUSHF stack
> exhausted
Peter,
These functions have a bunch of
Hi all,
Today's linux-next merge of the btrfs tree got a conflict in:
fs/btrfs/tree-log.c
between commit:
f135cea30de5 ("btrfs: fix partial loss of prealloc extent past i_size after
fsync")
from the btrfs-fixes tree and commit:
e94d318f12cd ("btrfs: fix partial loss of prealloc extent
Hi all,
Today's linux-next merge of the btrfs tree got a conflict in:
fs/btrfs/transaction.c
between commit:
fcc99734d1d4 ("btrfs: transaction: Avoid deadlock due to bad initialization
timing of fs_info::journal_info")
from the btrfs-fixes tree and commit:
f12ca53a6fd6 ("btrfs: force
On Thu, Apr 30, 2020 at 5:10 PM Linus Torvalds
wrote:
>
> It's a horrible word, btw. The word doesn't actually mean what Andy
> means it to mean. "fallible" means "can make mistakes", not "can
> fault".
Btw, on naming: the name should be about _why_ it can fault, not about
whether it faults.
> On Apr 30, 2020, at 5:10 PM, Linus Torvalds
> wrote:
>
> On Thu, Apr 30, 2020 at 4:52 PM Dan Williams
> wrote:
>>
>> You had me until here. Up to this point I was grokking that Andy's
>> "_fallible" suggestion does help explain better than "_safe", because
>> the copy is doing extra
From: Steven Rostedt (VMware)
Booting one of my machines, it triggered the following crash:
Kernel/User page tables isolation: enabled
ftrace: allocating 36577 entries in 143 pages
Starting tracer 'function'
BUG: unable to handle page fault for address: a05c
#PF: supervisor
On Sun, 16 Feb 2020 at 23:25, Stephen Rothwell wrote:
>
> Hi Arnaldo,
>
> On Thu, 30 Jan 2020 11:55:48 +0100 Arnaldo Carvalho de Melo
> wrote:
> >
> > Em Wed, Jan 29, 2020 at 08:58:29AM +0100, Jiri Olsa escreveu:
> > > On Tue, Jan 28, 2020 at 11:29:38PM +0800, Changbin Du wrote:
> > > > libbfd
On the official revision of coreboot for hatch it doesn't even try to
load Type C. However it gives some warning messages from
cros-usbpd-notify-acpi about EC, So I wonder why the check of the same
type is not appropriate in the typec driver?
../chrome/cros_usbpd_notify.c
/* Get the EC device
On Thu, Apr 30, 2020 at 4:52 PM Dan Williams wrote:
>
> You had me until here. Up to this point I was grokking that Andy's
> "_fallible" suggestion does help explain better than "_safe", because
> the copy is doing extra safety checks. copy_to_user() and
> copy_to_user_fallible() mean *something*
On Thu, Apr 30, 2020 at 11:43:20PM +0100, Filipe Manana wrote:
> On Thu, Apr 30, 2020 at 11:23 PM Dennis Zhou wrote:
> >
> > On Thu, Apr 30, 2020 at 02:40:18PM -0700, Andrew Morton wrote:
> > > On Thu, 30 Apr 2020 17:43:56 +0100 fdman...@kernel.org wrote:
> > >
> > > > From: Filipe Manana
> > >
On Thu, Apr 30, 2020 at 10:57 PM Michal Hocko wrote:
>
> On Wed 29-04-20 12:56:27, Johannes Weiner wrote:
> [...]
> > I think to address this, we need a more comprehensive solution and
> > introduce some form of serialization. I'm not sure yet how that would
> > look like yet.
>
> Yeah, that is
On 4/30/20 2:59 PM, Kirill A. Shutemov wrote:
On Thu, Apr 30, 2020 at 06:56:21AM +0800, Yang Shi wrote:
The max_ptes_{swap|none|shared} are defined to tune the behavior of
khugepaged. The are checked at a couple of places with open coding.
Replace the opencoding to
On Thu, Apr 30, 2020 at 12:56 PM Linus Torvalds
wrote:
>
> On Thu, Apr 30, 2020 at 12:23 PM Luck, Tony wrote:
> >
> > How about
> >
> > try_copy_catch(void *dst, void *src, size_t count, int *fault)
> >
> > returns number of bytes not-copied (like copy_to_user etc).
> >
> > if return is
The pull request you sent on Thu, 30 Apr 2020 11:59:00 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.7-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/75ec0ba2acf45cc31b5b59e00106a55494c62209
Thank you!
--
The pull request you sent on Thu, 30 Apr 2020 13:26:18 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-kunit-5.7-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0468915bdb7cd3160c892664a53ce320e254281e
Thank
The pull request you sent on Thu, 30 Apr 2020 08:57:43 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v5.7-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/af4a32ad21f83a0d093219c411e5a9f5b344e2ae
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 30 Apr 2020 17:24:20 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
> tags/selinux-pr-20200430
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/39e16d93424b61e0b5bd182e308a56d5f0e489d6
Thank you!
--
Icelake microserver CPU supports split lock detection while it doesn't
have the split lock enumeration bit in IA32_CORE_CAPABILITIES.
Enumerate the feature by model number.
Signed-off-by: Fenghua Yu
Reviewed-by: Tony Luck
---
arch/x86/kernel/cpu/intel.c | 1 +
1 file changed, 1 insertion(+)
Hi Rafael,
can you ACK this patch?
Regards,
Stefan
From: Stefan Berger
Recent extensions of the TPM2 ACPI table added 3 more fields
including 12 bytes of start method specific parameters and Log Area
Minimum Length (u32) and Log Area Start Address (u64). So, we extend
the existing
On Thu, Apr 30, 2020 at 2:24 PM Paul Moore wrote:
>
> Two more SELinux patches to fix problems in the v5.7-rcX releases.
> Wei Yongjun's patch fixes a return code in an error path, and my patch
> fixes a problem where we were not correctly applying access controls
> to all of the netlink messages
On Thu, 30 Apr 2020 at 21:32, Paolo Bonzini wrote:
>
> On 28/04/20 08:23, Wanpeng Li wrote:
> > - if (exit_fastpath == EXIT_FASTPATH_REENTER_GUEST &&
> > - kvm_vcpu_exit_request(vcpu))
> > - exit_fastpath = EXIT_FASTPATH_NOP;
> > + if (exit_fastpath ==
On Thu, Apr 30, 2020 at 07:38:55PM +0300, Andy Shevchenko wrote:
> On Thu, Apr 30, 2020 at 09:45:14PM +0530, Syed Nayyar Waris wrote:
> > On Wed, Apr 29, 2020 at 01:21:14PM +0300, Andy Shevchenko wrote:
> > > On Wed, Apr 29, 2020 at 04:39:47AM +0530, Syed Nayyar Waris wrote:
>
> ...
>
> > > > +
The side band interrupt service routine is not available on chips
like 7211, or rather, it does not permit the signaling of wake-up
events due to the complex interrupt hierarchy.
Move the wake-up event accounting into a .resume_noirq function,
account for possible wake-up events and clear the
On Thu, 2020-04-30 at 17:11 +0800, Kai-Heng Feng wrote:
> At the first time update_mute_led() gets called, if channels are
> already
> muted, the temp value equals to led_value as 0, skipping the
> following
> LED setting.
>
> So set led_value to -1 as an uninitialized state, to update the
>
On 4/30/20 3:19 PM, Sowjanya Komatineni wrote:
On 4/30/20 3:16 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:53 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:37 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:26 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:17 PM, Dmitry Osipenko wrote:
[Austin, help us understand the FIRMWARE_FIRST bit! :)]
On Thu, Apr 30, 2020 at 05:40:22PM -0500, Bjorn Helgaas wrote:
> On Sun, Apr 26, 2020 at 11:30:06AM -0700,
> sathyanarayanan.kuppusw...@linux.intel.com wrote:
> > From: Kuppuswamy Sathyanarayanan
> >
> >
> > Currently PCIe AER driver
On Thu, Apr 30, 2020 at 04:08:05PM -0500, Josh Poimboeuf wrote:
> On Thu, Apr 30, 2020 at 02:46:30PM -0500, Josh Poimboeuf wrote:
> > > Yup, makes sense. I think I've been getting confused by the syscall
> > > wrappers.
> > >
> > > > How hard would it be to change objtool instead of changing the
This fixes:
Documentation/misc-devices/uacce.rst: WARNING: document isn't included in any
toctree
Signed-off-by: Vitor Massaru Iha
---
Documentation/misc-devices/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/misc-devices/index.rst
This fixes:
Documentation/misc-devices/uacce.rst: WARNING: document isn't included in any
toctree
Signed-off-by: Vitor Massaru Iha
---
Documentation/misc-devices/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/misc-devices/index.rst
On Thu, Apr 30, 2020 at 11:23 PM Dennis Zhou wrote:
>
> On Thu, Apr 30, 2020 at 02:40:18PM -0700, Andrew Morton wrote:
> > On Thu, 30 Apr 2020 17:43:56 +0100 fdman...@kernel.org wrote:
> >
> > > From: Filipe Manana
> > >
> > > Since 5.7-rc1, on btrfs we have a percpu counter initialization for
[+cc Austin, Mario, Jon, Alex, Rafael, Keith, Sinan, Tyler]
On Sun, Apr 26, 2020 at 11:30:06AM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> Currently PCIe AER driver uses HEST FIRMWARE_FIRST bit to
> determine the PCIe AER Capability ownership
Schönen Tag:
Mein Name Mark Anderson, Direktor einer privaten Kreditagentur Blemain
Finance Ltd Großbritannien.
Ich bin hier, um ein Darlehensprogramm vorzustellen, das dazu beiträgt, Ihre
finanzielle und wirtschaftliche Situation zu verbessern und Sie von allen
Finanzkrisen /
Hi folks,
We're working on trying to figure out a severe performance regression in
the 5.4 and older LTS trees. The regression seems to happen only on
physical spinning rust disks, which is why it was probably went
unnoticed.
The regression seems to be introduced in v4.7 with:
On 4/30/20 9:47 PM, Niklas Schnelle wrote:
>
>
> On 4/30/20 5:58 PM, Saeed Mahameed wrote:
>> On Thu, 2020-04-30 at 14:03 +0200, Niklas Schnelle wrote:
>>> as described in Documentation/PCI/pci-iov-howto.rst a driver with SR-
>>> IOV
>>> support should call pci_disable_sriov() in the remove
On 2020-04-30 12:54, Christian Borntraeger wrote:
On 30.04.20 21:02, Christian Borntraeger wrote:
On 30.04.20 20:12, Christian Borntraeger wrote:
On 29.04.20 18:07, Dave Hansen wrote:
On 4/28/20 3:50 PM, Claudio Imbrenda wrote:
If a page is inaccesible and it is used for things like
> My guess is that at least with the pending ofono patches, we just
> want to use the raw interface for /dev/gsmtty* interface and stop
> pretending we have a modem that is AT compatible.
I tried to get it to work... it was not fun and I did not get far.
I pushed my results...
On Thu, Apr 30, 2020 at 02:40:18PM -0700, Andrew Morton wrote:
> On Thu, 30 Apr 2020 17:43:56 +0100 fdman...@kernel.org wrote:
>
> > From: Filipe Manana
> >
> > Since 5.7-rc1, on btrfs we have a percpu counter initialization for which
> > we always pass a GFP_KERNEL gfp_t argument (this happens
On Thu, 30 Apr 2020 20:43:39 +0200 David Hildenbrand wrote:
> >
> > Why does the firmware map support hotplug entries?
>
> I assume:
>
> The firmware memmap was added primarily for x86-64 kexec (and still, is
> mostly used on x86-64 only IIRC). There, we had ACPI hotplug. When DIMMs
> get
Binding in Documentation is still "operating-points-v2-kryo-cpu".
Restore the old binding to fix the compatibility problem.
Fixes: a8811ec764f9 ("cpufreq: qcom: Add support for krait based socs")
Signed-off-by: Ansuel Smith
---
drivers/cpufreq/qcom-cpufreq-nvmem.c | 2 +-
1 file changed, 1
Translation for the following patches:
commit c4f4af4094d6 ("docs: Add documentation for Symbol Namespaces")
commit 36bc683dde0a ("kernel-doc: rename the kernel-doc directive 'functions'
to 'identifiers'")
commit a035d552a93b ("Makefile: Globally enable fall-through warning")
commit b9918bdcac1f
On 4/30/20 3:16 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:53 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:37 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:26 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:17 PM, Dmitry Osipenko wrote:
30.04.2020 23:02, Sowjanya Komatineni пишет:
On
One other thing... The gup code will not take references on ref-frozen
pages:
> static inline __must_check bool try_get_page(struct page *page)
> {
> page = compound_head(page);
> if (WARN_ON_ONCE(page_ref_count(page) <= 0))
> return false;
>
On 4/30/20 2:53 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:37 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:26 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:17 PM, Dmitry Osipenko wrote:
30.04.2020 23:02, Sowjanya Komatineni пишет:
On 4/30/20 12:53 PM, Sowjanya Komatineni wrote:
On
This series removes a field that holds a copy of a channel's state
at the time it was last fetched. In principle the state can change
at any time, so it's better to just fetch it whenever needed. The
first patch is just preparatory, simplifying the arguments to
gsi_channel_state().
Pass a channel pointer rather than a GSI pointer and channel ID to
gsi_channel_state().
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ipa/gsi.c b/drivers/net/ipa/gsi.c
index
On Thu, Apr 30, 2020 at 11:44:42PM +0200, Guoqing Jiang wrote:
> +/**
> + * attach_page_private - attach data to page's private field and set
> PG_private.
> + * @page: page to be attached and set flag.
> + * @data: data to attach to page's private field.
> + *
> + * Need to take reference as
It is possible for a GSI channel's state to be changed as a result
of an action by a different execution environment. Specifically,
the modem is able to issue a GSI generic command that causes a state
change on a GSI channel associated with the AP.
A channel's state only needs to be known when a
This fixes:
Documentation/s390/vfio-ap.rst:488: WARNING: duplicate label
s390/vfio-ap:guest2, other instance in
/home/iha/sdb/opensource/lkmp/linux_doc/Documentation/s390/vfio-ap.rst
Signed-off-by: Vitor Massaru Iha
---
Documentation/s390/vfio-ap.rst | 2 +-
1 file changed, 1 insertion(+), 1
Hi Robin,
> On Apr 8, 2020, at 9:49 AM, Robin Murphy wrote:
>
> IRQF_SHARED is dangerous, since it allows other agents to retarget the
> IRQ's affinity without migrating PMU contexts to match, breaking the way
> in which perf manages mutual exclusion for accessing events. Although
> this means
Hi,
Am Do., 30. Apr. 2020 um 23:56 Uhr schrieb Guoqing Jiang
:
> The logic in attach_page_buffers and __clear_page_buffers are quite
> paired, but
>
> 1. they are located in different files.
>
> 2. attach_page_buffers is implemented in buffer_head.h, so it could be
>used by other files. But
Sometimes it's not okay to use SIMD registers, the conditions for which
have changed subtly from kernel release to kernel release. Usually the
pattern is to check for may_use_simd() and then fallback to using
something slower in the unlikely case SIMD registers aren't available.
So, this patch
I was also wondering if Claudio was right about the debug patch having
races. I went to go look how the s390 code avoids races when pages go
from accessible->inaccessible.
Because, if if all of the traps are in place to transform pages from
inaccessible->accessible, the code *after* those traps
From: Sham Muthayyan
Add Force GEN1 support needed in some ipq8064 board that needs to limit
some PCIe line to gen1 for some hardware limitation.
This is set by the max-link-speed binding and needed by some soc based
on ipq8064. (for example Netgear R7800 router)
Signed-off-by: Sham Muthayyan
It is now supported the editing of Tx De-Emphasis, Tx Swing and
Rx equalization params on ipq8064. Document this new optional params.
Signed-off-by: Ansuel Smith
---
.../devicetree/bindings/pci/qcom,pcie.txt | 36 +++
1 file changed, 36 insertions(+)
diff --git
Document ext reset used in ipq8064 SoC by qcom PCIe driver.
Signed-off-by: Ansuel Smith
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
Document qcom,pcie-ipq8064-v2 needed to use different phy_tx0_term_offset.
In ipq8064 phy_tx0_term_offset is 7.
In ipq8064 v2 other SoC it's set to 0 by default.
Signed-off-by: Ansuel Smith
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
Add missing ext reset used by ipq8064 SoC in PCIe qcom driver.
Fixes: 82a823833f4e PCI: qcom: Add Qualcomm PCIe controller driver
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
Cc: sta...@vger.kernel.org # v4.5+
---
drivers/pci/controller/dwc/pcie-qcom.c | 12
1 file
Use qcom_clear_and_set_dword instead of use the same code many times in
the entire driver.
Signed-off-by: Ansuel Smith
---
drivers/pci/controller/dwc/pcie-qcom.c | 108 ++---
1 file changed, 41 insertions(+), 67 deletions(-)
diff --git
Document missing clks used in ipq8064 soc.
Signed-off-by: Ansuel Smith
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
From: Abhishek Sahu
The deinit issues reset_control_assert for PCI twice and does not contain
phy reset.
Signed-off-by: Abhishek Sahu
Signed-off-by: Ansuel Smith
---
drivers/pci/controller/dwc/pcie-qcom.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git
From: Sham Muthayyan
Add tx term offset support to pcie qcom driver need in some revision of
the ipq806x SoC.
Ipq8064 have tx term offset set to 7.
Ipq8064-v2 revision and ipq8065 have the tx term offset set to 0.
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
---
Add support for Tx De-Emphasis, Tx Swing and Rx equalization definition
needed on some ipq8064 based device (Netgear R7800 for example). This
cause a total lock of the system on kernel load.
Fixes: 82a823833f4e PCI: qcom: Add Qualcomm PCIe controller driver
Signed-off-by: Ansuel Smith
Cc:
This contains multiple fix for PCIe qcom driver.
Some optional reset and clocks were missing.
Fix a problem with no PARF programming that cause kernel lock on load.
Add support to force gen 1 speed if needed. (due to hardware limitation)
Add ipq8064 rev 2 support that use a different tx
Aux and Ref clk are missing in PCIe qcom driver.
Add support in the driver to fix PCIe initialization in ipq806x.
Fixes: 82a823833f4e PCI: qcom: Add Qualcomm PCIe controller driver
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
Cc: sta...@vger.kernel.org # v4.5+
---
Hi Paul,
> The PX30 features a RGA block: add the necessary node to support it.
>
> Signed-off-by: Paul Kocialkowski
> ---
> arch/arm64/boot/dts/rockchip/px30.dtsi | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/px30.dtsi
>
On Thu, Apr 30, 2020 at 06:56:21AM +0800, Yang Shi wrote:
> The max_ptes_{swap|none|shared} are defined to tune the behavior of
> khugepaged. The are checked at a couple of places with open coding.
> Replace the opencoding to exceed_pax_ptes_{swap|none_shared} helpers to
> improve the
On 4/13/20 10:27 AM, Tejun Heo wrote:
> Changes from v1[1]
>
> * Dropped 0002-block-add-request-io_data_len.patch and updated to use
> rq->stats_sectors instead as suggested by Pavel Begunkov.
>
> This patchset improves the following two iocost control behaviors.
>
> * iocost was failing to
On 4/30/20 2:37 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:26 PM, Sowjanya Komatineni wrote:
On 4/30/20 2:17 PM, Dmitry Osipenko wrote:
30.04.2020 23:02, Sowjanya Komatineni пишет:
On 4/30/20 12:53 PM, Sowjanya Komatineni wrote:
On 4/30/20 12:46 PM, Sowjanya Komatineni wrote:
On
On Thursday 30 April 2020 23:30:51 Arnd Bergmann wrote:
> gcc-10 warns about writes to the empty freeSpaceTable[] array, with
> many instances like:
>
> fs/udf/balloc.c: In function 'udf_bitmap_new_block':
> fs/udf/balloc.c:101:36: error: array subscript 65535 is outside the bounds of
> an
101 - 200 of 1652 matches
Mail list logo
