Hi
I tried running a simple test:
dd if=testfile iflag=direct bs=1M of=/dev/null
With my default settings, `vmstat 10` shows something like 85% idle time
to 15% iowait time. I have 4 CPUs, so this is much less than one CPU
worth of iowait time.
If I boot with "nohz=off", I see idle time
From: "Raju P.L.S.S.S.N"
tcs->lock was introduced to serialize access with in TCS group. But
even without tcs->lock, drv->lock is serving the same purpose. So
use a single drv->lock.
Other optimizations include -
- Remove locking around clear_bit() in IRQ handler. clear_bit() is
atomic.
- R
When triggering a TCS to send its contents, reading back the trigger
value may return an incorrect value. That is because, writing the
trigger may raise an interrupt which could be handled immediately and
the trigger value could be reset in the interrupt handler. By doing a
read back we may end up
On Mon, 2019-07-01 at 06:45 +0700, Phong Tran wrote:
> This is for fixing bug KMSAN: uninit-value in ax88772_bind
>
> Tested by
> https://groups.google.com/d/msg/syzkaller-bugs/aFQurGotng4/cFe9nxMCCwAJ
>
> Reported-by: syzbot+8a3fc6674bbc3978e...@syzkaller.appspotmail.com
>
> syzbot found the fo
Hi Aniket,
On 6/26/19 11:23 AM, Aniket Masule wrote:
> This patch introduces bitrate based clock scaling. Also, clock scaling is now
> triggered before buffer being queued to the device. This checks for frequency
> requirement throughout the session and updates clock with correct frequency
> only
This commit document changes after split vsc73xx driver into core and
spi part. The change of DT bindings is required for support the same
vsc73xx chip, which need PI bus to communicate with CPU. It also
introduce how to use vsc73xx platform driver.
Signed-off-by: Pawel Dembicki
---
.../bindings
Driver allow to use devices with disabled iCPU only.
Some devices have pre-initialised iCPU by bootloader.
That state make switch unmanaged. This patch force reset
if device is in unmanaged state. In the result chip lost
internal firmware from RAM and it can be managed.
Signed-off-by: Pawel Dembi
This driver (currently) only takes control of the switch chip over
SPI and configures it to route packages around when connected to a
CPU port. But Vitesse chip support also parallel interface.
This patch split driver into two parts: core and spi. It is required
for add support to another managing
This patch add platform part of vsc73xx driver.
It allows to use chip connected by PI interface.
Signed-off-by: Pawel Dembicki
---
drivers/net/dsa/Kconfig| 8 +
drivers/net/dsa/Makefile | 1 +
drivers/net/dsa/vitesse-vsc73xx-platform.c | 166
From: Markus Elfring
Date: Mon, 1 Jul 2019 17:10:13 +0200
A single character (depending on a condition check) should be put
into a sequence. Thus use the corresponding function “seq_putc”.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/md/r
Hi Arnd,
On Mon, Jul 1, 2019 at 10:52 PM Arnd Bergmann wrote:
>
> On Sat, Jun 29, 2019 at 7:36 AM wrote:
> >
> > From: Guo Ren
> >
> > These codes are copied from glibc/string directory, they are the generic
> > implementation for string operations. We may further optimize them with
> > assembl
On 01-07-19, 17:01, Jorge Ramirez-Ortiz wrote:
> mutexes can sleep and therefore should not be taken while holding a
> spinlock. move clk_get_rate (can sleep) outside the spinlock protected
> region.
Reviewed-by: Vinod Koul
--
~Vinod
Use the managed API of the LED class (devm_led_classdev_register()
instead of led_classdev_register()).
This allows us to remove the code used to track-and-destroy the LED devices
Signed-off-by: Jean-Jacques Hiblot
---
drivers/leds/leds-tlc591xx.c | 81 ++--
1 fil
This mini-series updates the tlc591xx driver to use the managed API. The
driver is also modified to pass the DT node to the LED core layer.
The goal is to be able to the generic led-backlight [0] driver on top of
it.
[0] https://lore.kernel.org/patchwork/project/lkml/list/?series=400524
Jean-Jacq
The driver parses the device-tree to identify which LED should be handled.
Since the information about the device node is known at this time, we can
provide the LED core with it. It may be useful later.
Signed-off-by: Jean-Jacques Hiblot
---
drivers/leds/leds-tlc591xx.c | 2 +-
1 file changed, 1
On Mon, Jul 01, 2019 at 05:14:51PM +0200, Arnd Bergmann wrote:
> On Fri, Jun 21, 2019 at 5:30 PM Christian Brauner
> wrote:
> > On Fri, Jun 21, 2019 at 04:20:15PM +0200, Arnd Bergmann wrote:
> > > On Fri, Jun 21, 2019 at 1:18 PM Christian Brauner
> > > wrote:
> > Hm, if you believe that this is
On Wed, Jun 19, 2019 at 02:28:33PM -0500, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct v
On Mon, 2019-07-01 at 14:32 +0300, Andy Shevchenko wrote:
> On Sun, Jun 30, 2019 at 8:14 PM Srinivas Pandruvada
> wrote:
> >
> > The Intel(R) Speed select technologies contains four features.
> >
> > Performance profile:An non architectural mechanism that allows
> > multiple
> > optimized perfor
There wasn't any actual need to add a real pud_page, as pud_huge
always returns false on sh. Just stub it out to fix the sh3
compile failure.
Fixes: 937b4e1d6471 ("sh: add the missing pud_page definition")
Reported-by: Guenter Roeck
Signed-off-by: Christoph Hellwig
---
arch/sh/include/asm/pgta
Hi Andrew,
below two fixups for the generic GUP series, as reported by Guenter.
MIPS doesn't really have a proper pte_special implementation, just
stubs. It turns out they were not enough to make get_user_pages_fast
work, so drop the select. This means get_user_pages_fast won't
actually use the fast path for non-hugepage mappings, so someone who
actually knows about mips pag
On Mon, Jul 01, 2019 at 04:59:04PM +0200, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> >
> > Dmitry, any idea why syzbot found such a bizarre reproducer for this?
> > This is actually reproducible by a simple single threaded program:
> >
> > #include
> >
> > #define __NR_move_mount
On Fri, Jun 21, 2019 at 5:30 PM Christian Brauner wrote:
> On Fri, Jun 21, 2019 at 04:20:15PM +0200, Arnd Bergmann wrote:
> > On Fri, Jun 21, 2019 at 1:18 PM Christian Brauner
> > wrote:
> Hm, if you believe that this is fine and want to "vouch" for it by
> whipping up a patch that replaces the
On Fri, Jun 28, 2019 at 02:36:56PM +0200, Stefano Garzarella wrote:
> During the review of "[PATCH] vsock/virtio: Initialize core virtio vsock
> before registering the driver", Stefan pointed out some possible issues
> in the .probe() and .remove() callbacks of the virtio-vsock driver.
>
> This se
On 25/06/19 10:19 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> We need to enable status changes for the fixed power supply for the USB
> controller.
>
> Fixes: 274e4c336192 ("ARM: davinci: da830-evm: add a fixed regulator for
> ohci-da8xx")
> Cc: sta...@vger.kernel.org
> Signe
On Fri, Jun 28, 2019 at 02:36:57PM +0200, Stefano Garzarella wrote:
> Some callbacks used by the upper layers can run while we are in the
> .remove(). A potential use-after-free can happen, because we free
> the_virtio_vsock without knowing if the callbacks are over or not.
>
> To solve this issue
On Fri, Jun 28, 2019 at 02:36:59PM +0200, Stefano Garzarella wrote:
> This patch moves the flush of works after vdev->config->del_vqs(vdev),
> because we need to be sure that no workers run before to free the
> 'vsock' object.
>
> Since we stopped the workers using the [tx|rx|event]_run flags,
> w
On 25/06/19 8:46 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The fixed regulator driver doesn't specify any con_id for gpio lookup
> so it must be NULL in the table entry.
>
> Fixes: 274e4c336192 ("ARM: davinci: da830-evm: add a fixed regulator for
> ohci-da8xx")
> Cc: sta...
On Fri, Jun 28, 2019 at 02:36:59PM +0200, Stefano Garzarella wrote:
> This patch moves the flush of works after vdev->config->del_vqs(vdev),
> because we need to be sure that no workers run before to free the
> 'vsock' object.
>
> Since we stopped the workers using the [tx|rx|event]_run flags,
> w
On Mon, 01 Jul 2019 08:54:44 -0600
Alex Williamson wrote:
> This allows udev to trigger rules when a parent device is registered
> or unregistered from mdev.
>
> Signed-off-by: Alex Williamson
> ---
>
> v2: Don't remove the dev_info(), Kirti requested they stay and
> removing them is only
The i2c-dev module is for access to I2C buses from user-space.
Kernel drivers do not care about its presence.
Signed-off-by: Jean Delvare
Cc: Matt Sickler
Cc: Greg Kroah-Hartman
---
drivers/staging/kpc2000/kpc_i2c/i2c_driver.c |1 -
1 file changed, 1 deletion(-)
--- linux-5.2-rc7.orig/dri
On Fri, Jun 28, 2019 at 6:32 PM David Miller wrote:
>
> From: Arnd Bergmann
> Date: Fri, 28 Jun 2019 12:31:44 +0200
>
> > On 32-bit architectures, putting an array of 256 u32 values on the
> > stack uses more space than the warning limit:
> >
> > drivers/net/ethernet/huawei/hinic/hinic_main.c: In
On Fri, Jun 28, 2019 at 9:53 PM Paul Cercueil wrote:
> Le jeu. 27 juin 2019 à 18:40, Miquel Raynal
> a écrit :
> > Miquel Raynal wrote on Mon, 17 Jun 2019
> > 14:16:59 +0200:
> >> I personally have a preference for this one.
> >
> > Would you mind sending the above change? I forgot about it bu
mutexes can sleep and therefore should not be taken while holding a
spinlock. move clk_get_rate (can sleep) outside the spinlock protected
region.
Fixes: 83736352e0ca ("mmc: sdhci-msm: Update DLL reset sequence")
Cc: sta...@vger.kernel.org
Signed-off-by: Jorge Ramirez-Ortiz
Reviewed-by: Bjorn And
On Sat, Jun 29, 2019 at 10:39 PM Eric Biggers wrote:
>
> On Mon, Jun 24, 2019 at 11:28:18AM +0200, 'Dmitry Vyukov' via syzkaller-bugs
> wrote:
> > On Tue, Jun 18, 2019 at 4:03 PM Al Viro wrote:
> > >
> > > On Tue, Jun 18, 2019 at 03:47:10AM -0700, syzbot wrote:
> > > > Hello,
> > > >
> > > > syz
On Fri, Jun 28, 2019 at 01:11:51PM +0200, Thomas Gleixner wrote:
> But that does not catch the case where the interrupt is on flight at the
> hardware level but not yet serviced by the target CPU. That creates an
> interesing race condition:
> + * It does not check whether there is an interrupt
This allows udev to trigger rules when a parent device is registered
or unregistered from mdev.
Signed-off-by: Alex Williamson
---
v2: Don't remove the dev_info(), Kirti requested they stay and
removing them is only tangential to the goal of this change.
drivers/vfio/mdev/mdev_core.c |
On Fri, Jun 28, 2019 at 5:59 PM Jaegeuk Kim wrote:
>
> Hi Arnd,
>
> If you don't mind, can I integrate this into the original patch in the queue?
Yes, I think that would be good anyway, it may take a little longer to fix all
the architectures.
Arnd
On Fri, Jun 28, 2019 at 02:36:57PM +0200, Stefano Garzarella wrote:
> Some callbacks used by the upper layers can run while we are in the
> .remove(). A potential use-after-free can happen, because we free
> the_virtio_vsock without knowing if the callbacks are over or not.
>
> To solve this issue
On Fri, Jun 28, 2019 at 01:11:50PM +0200, Thomas Gleixner wrote:
> The function might sleep, so it cannot be called from interrupt
> context. Not even with care.
>
> Signed-off-by: Thomas Gleixner
> ---
> kernel/irq/manage.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> --- a
On Mon, Jul 01, 2019 at 02:02:35PM +0200, Paolo Bonzini wrote:
> On 01/07/19 09:50, Li Wang wrote:
> > Hello there,
> >
> > LTP/umip_basic_test get failed on KVM UMIP
> > system(kernel-v5.2-rc4.x86_64). The test is only trying to do
> > asm volatile("smsw %0\n" : "=m" (val));
> > and expect t
On Sat, Jun 29, 2019 at 7:36 AM wrote:
>
> From: Guo Ren
>
> These codes are copied from glibc/string directory, they are the generic
> implementation for string operations. We may further optimize them with
> assembly code in the future.
>
> In fact these code isn't tested enough for kernel, but
Hello,
On Mon, Jul 01, 2019 at 10:27:31AM +0200, Peter Zijlstra wrote:
> IIRC TJ figured it wasn't strictly required to fix the lock invertion at
> that time and they sorted it differently. If I (re)read the thread
> correctly the other day, he didn't have fundamental objections against
> it, but
On Mon, Jun 24, 2019 at 10:55:41AM +0100, Raphael Gault wrote:
> Until now, the section .altinstr_replacement wasn't marked as containing
> executable instructions on arm64. This patch changes that so that it is
> coherent with what is done on x86.
>
> Signed-off-by: Raphael Gault
> ---
> arch/a
On Mon, Jul 01, 2019 at 04:48:08PM +0200, Christian Brauner wrote:
> Make sure to return a proper negative error code from copy_process()
> when anon_inode_getfile() fails with CLONE_PIDFD.
> Otherwise _do_fork() will not detect an error and get_task_pid() will
> operator on a nonsensical pointer:
On Mon 01 Jul 03:53 PDT 2019, Jorge Ramirez-Ortiz wrote:
> mutexes can sleep and therefore should not be taken while holding a
> spinlock. move clk_get_rate (can sleep) outside the spinlock protected
> region.
>
> This regression was introduced with commit
> Date: Mon Nov 21 12:07:16 2016
On Mon, Jul 1, 2019 at 4:14 PM Joel Fernandes wrote:
>
> On Mon, Jul 01, 2019 at 02:23:58PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2019-07-01 00:04:15 [-0400], Joel Fernandes (Google) wrote:
> > > This reverts commit a6fda6dab93c2c06ef4b8cb4b9258df6674d2438 which
> > > causes kvm.sh to not
Make sure to return a proper negative error code from copy_process()
when anon_inode_getfile() fails with CLONE_PIDFD.
Otherwise _do_fork() will not detect an error and get_task_pid() will
operator on a nonsensical pointer:
R10: R11: 0246 R12: 006dbc2c
R13: 000
On 28/06/19 4:17 PM, Arnd Bergmann wrote:
> [I missed the davinci maintainers on cc here, sorry]
>
> On Fri, Jun 28, 2019 at 12:41 PM Arnd Bergmann wrote:
>>
>> When building davinci as multiplatform, we get a build error
>> in this file:
>>
>> drivers/mfd/davinci_voicecodec.c:22:10: fatal error:
On Mon, Jun 24, 2019 at 10:55:42AM +0100, Raphael Gault wrote:
> --- a/arch/arm64/include/asm/assembler.h
> +++ b/arch/arm64/include/asm/assembler.h
> @@ -752,4 +752,17 @@ USER(\label, ic ivau, \tmp2)//
> invalidate I line PoU
> .Lyield_out_\@ :
> .endm
>
> + /*
>
On Mon, Jul 01, 2019 at 09:46:30AM +0200, Peter Zijlstra wrote:
> On Fri, Jun 28, 2019 at 05:49:52PM -0700, Michel Lespinasse wrote:
> > The motivation for this change is that I want to introduce augmented rbtree
> > uses where the augmented data for the subtree is a struct instead of a
> > scala
On Fri, Jun 21, 2019 at 7:22 PM Bjorn Andersson
wrote:
>
> In some software releases the firmware images are not split up with each
> loadable segment in it's own file. Check the size of the loaded firmware
> to see if it still contains each segment to be loaded, before falling
> back to the split
On Fri, Jun 21, 2019 at 7:22 PM Bjorn Andersson
wrote:
>
> In some software releases the firmware images are not split up with each
> loadable segment in it's own file. Check the size of the loaded firmware
> to see if it still contains each segment to be loaded, before falling
> back to the split
On 28/06/19 4:21 PM, Arnd Bergmann wrote:
> The driver builds fine without these, and they cause build
> problems once davinci multiplatform support is enabled.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Sekhar Nori
Thanks,
Sekhar
Hello, I'm also still experiencing this issue on 5.1.15. It's making it
very difficult to use my work laptop in my office, since it has many
access points and frequently has to reauthenticate. I hit this bug 1-3
times per day, and the only way to fix it is a hard shutdown. Has there
been any effort
On Sun, Jun 16, 2019 at 03:56:19AM +0800, Bjorn Helgaas wrote:
> [+cc Ben, Logan]
>
> Ben, Logan, since you're looking at the resource code, maybe you'd be
> interested in this as well?
>
> On Wed, May 22, 2019 at 02:30:30PM +, Nicholas Johnson wrote:
> > Rebase patches to apply cleanly to 5.
Obviously functions that are safe to be called from atomic contexts, can
be called from non-atomic contexts, too.
Signed-off-by: Geert Uytterhoeven
---
Do I need more coffee?
---
drivers/gpio/gpiolib.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/g
On Mon, Jul 01, 2019 at 02:07:55PM +0300, Alexander Shishkin wrote:
> So far, we tried to disallow grouping exclusive events for the fear of
> complications they would cause with moving between contexts. Specifically,
> moving a software group to a hardware context would violate the exclusivity
> r
Commit 372e722ea4dd4ca1 ("gpiolib: use descriptors internally") renamed
the functions to use a "gpiod" prefix, and commit 79a9becda8940deb
("gpiolib: export descriptor-based GPIO interface") introduced the "raw"
variants, but both changes forgot to update the comments.
Readd a similar reference to
A new field init_valid_mask was added to struct gpio_chip, but it was
not documented.
Fixes: f8ec92a9f63b3b11 ("gpiolib: Add init_valid_mask exported function")
Signed-off-by: Geert Uytterhoeven
---
include/linux/gpio/driver.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/g
Background
==
Currently, the kernel can sometimes assign the MMIO_PREF window
additional size into the MMIO window, resulting in double the MMIO
additional size, even if the MMIO_PREF window was successful.
This happens if in
On 7/1/19 9:42 AM, Nikolaus Voss wrote:
> Replace enum tas572x_type with struct tas5720_variant which aggregates
> variant specific stuff and can be directly referenced from an id table.
>
> Signed-off-by: Nikolaus Voss
> ---
> sound/soc/codecs/tas5720.c | 98 +---
Add kernel parameter pci=hpmmiosize=nn[KMG] to set MMIO bridge window
size for hotplug bridges.
Add kernel parameter pci=hpmmioprefsize=nn[KMG] to set MMIO_PREF bridge
window size for hotplug bridges.
Leave pci=hpmemsize=nn[KMG] unchanged, to prevent disruptions to
existing users. This sets both
Remove checks for resource size in extend_bridge_window(). This is
necessary to allow the pci_bus_distribute_available_resources() to
function when the kernel parameter pci=hpmemsize=nn[KMG] is used to
allocate resources. Because the kernel parameter sets the size of all
hotplug bridges to be the s
Change extend_bridge_window() to set resource size directly instead of
using additional resource lists.
Because additional resource lists are optional resources, any algorithm
that requires guaranteed allocation that uses them cannot be guaranteed
to work.
Remove the resource from add_list. If it
In extend_bridge_window() change "available" parameter name to new_size.
This makes more sense as this parameter represents the new size for the
window.
Signed-off-by: Nicholas Johnson
---
drivers/pci/setup-bus.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers
Rewrite pci_bus_distribute_available_resources to better handle bridges
with different resource alignment requirements. Pass more details
arguments recursively to track the resource start and end addresses
relative to the initial hotplug bridge. This is especially useful for
Thunderbolt with native
If "hotplug_bridges == 0", "!dev->is_hotplug_bridge" is always true, so the
loop that divides the remaining resources among hotplug-capable bridges
does nothing.
Check for "hotplug_bridges == 0" earlier, so we don't even have to compute
the amount of remaining resources. No functional change inte
On 6/30/19 5:06 PM, Hugh Dickins wrote:
> On Wed, 5 Jun 2019, Jens Axboe wrote:
>>
>> How about the following plan - if folks are happy with this sched patch,
>> we can queue it up for 5.3. Once that is in, I'll kill the block change
>> that special cases the polled task wakeup. For 5.2, we go with
Reorder pci_bus_distribute_available_resources() to group related code
together. No functional change intended.
Link:
https://lore.kernel.org/r/ps2p216mb0642c7a485649d2d787a1c6f80...@ps2p216mb0642.korp216.prod.outlook.com
Based-on-patch-by: Nicholas Johnson
[bhelgaas: extracted from larger patc
On Mon, 2019-07-01 at 13:55 +0200, Lukas Wunner wrote:
> I see. In that case, try:
>
> /* handle all the 3-wire mode */
> - if ((spi->mode & SPI_3WIRE) && (tfr->rx_buf))
> + if ((spi->mode & SPI_3WIRE) && (tfr->rx_buf != ctlr->dummy_rx))
> cs |= BCM2835_SPI_CS_REN;
>
On Mon, 1 Jul 2019, Oliver Neukum wrote:
> Am Mittwoch, den 26.06.2019, 10:38 -0400 schrieb Alan Stern:
> > On Wed, 26 Jun 2019, Oliver Neukum wrote:
> >
> > > Am Montag, den 24.06.2019, 10:22 -0400 schrieb Alan Stern:
> > > > But that pattern makes no sense; a driver would never use it. The
>
Included patches from Bjorn. I had already started my own equivalent
patches, but it will be easier for Bjorn to sign off if he wrote them.
Moved the bug fix to the end of the series, in case we accept Logan's
equivalent patch instead - in which case, the last patch in my series
can easily be drop
Fix GUE_PFLAG_REMCSUM to use "U" cast to avoid shifting signed
32-bit value by 31 bits problem.
Signed-off-by: Vandana BN
---
include/net/gue.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/net/gue.h b/include/net/gue.h
index fdad41469b65..3a6595bfa641 100644
--- a/
On Mon, Jul 01, 2019 at 02:23:58PM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-07-01 00:04:15 [-0400], Joel Fernandes (Google) wrote:
> > This reverts commit a6fda6dab93c2c06ef4b8cb4b9258df6674d2438 which
> > causes kvm.sh to not run on my machines. The qemu-system-x86_64 command
> > runs but
On Sat, 29 Jun 2019, Andrea Parri wrote:
> The formal memory consistency model has added support for plain accesses
> (and data races). While updating the informal documentation to describe
> this addition to the model is highly desirable and important future work,
> update the informal documenta
On Mon, Jul 01, 2019 at 12:39:35PM +0200, John Ogness wrote:
> On 2019-06-28, Peter Zijlstra wrote:
> > (Note that the qspinlock has a queue not unlike this, but that again
> > doesn't have to bother with NMIs)
>
> Thank you for pointing this out! I will look to qspinlock for some
> naming guidel
On Mon, Jul 01, 2019 at 12:39:35PM +0200, John Ogness wrote:
> Thanks. I overlooked that subtle detail. Can I assume NMIs do not exist
> on architectures that need to implement locking for cmpxchg()? Or did I
> just hit a major obstacle?
I think that is a fair assumption, I'm not aware of anybody
On Wed, 26 Jun 2019 23:22:19 +0200,
Evan Green wrote:
>
> The widget_mutex was introduced to serialize callers to
> hda_widget_sysfs_{re}init. However, its protection of the sysfs widget array
> is incomplete. For example, it is acquired around the call to
> hda_widget_sysfs_reinit(), which actual
Hi Ted,
On Mon, Jul 1, 2019 at 3:56 PM Theodore Ts'o wrote:
> On Mon, Jul 01, 2019 at 02:43:14PM +0200, Geert Uytterhoeven wrote:
> > Despite this fix having been applied upstream, the kernel prints from
> > time to time:
> >
> > EXT4-fs (sda1): error count since last fsck: 5
> > EXT4-fs
On Mon, Jul 01, 2019 at 02:55:52PM +0100, Patrick Bellasi wrote:
> On 01-Jul 11:02, Peter Zijlstra wrote:
> > Hmmm?
>
> Just one more requirement I think it's worth to consider since the
> beginning: CGroups support
>
> That would be very welcome interface. Just because is so much more
> conveni
Hello
I need your urgent assistance in the transfer of an abandoned funds
on your account within 10-14 days if you are interested, respond to me
with your information for more details. your name and surname:-. your
country:-. your phone number. :- .
Please respond to this email address (sergeami.
On Mon, Jul 01, 2019 at 02:55:52PM +0100, Patrick Bellasi wrote:
> On 01-Jul 11:02, Peter Zijlstra wrote:
> > Some of the things we could tie to this would be:
> >
> > - select_idle_siblings; -nice would scan more than +nice,
>
> Just to be sure, you are not proposing to use the nice value we
Hello Tetsuo,
On Mon, 1 Jul 2019 at 17:07, Laura Abbott wrote:
>
> On 7/1/19 6:55 AM, Tetsuo Handa wrote:
> > Andrew, can you pick up this patch? No response from Laura Abbott nor Sumit
> > Semwal.
Apologies; it didn't seem to get flitered out for me. I'll re-check my
email filters.
> >
> > On 2
On Mon, Jul 01, 2019 at 05:23:05AM -0700, Paul E. McKenney wrote:
> On Mon, Jul 01, 2019 at 12:24:42PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2019-07-01 11:42:15 [+0200], Peter Zijlstra wrote:
> > > I'm not sure if smp_send_reschedule() can be used as self-IPI, some
> > > hardware doesn't p
When using the legacy clock framework, clock pointers are no longer
printed as IDs, as the !CONFIG_COMMON_CLK case was accidentally
considered an error case.
Fix this by reverting to the old behavior, which allows to distinguish
clocks by ID, as the legacy clock framework does not store names with
The information which is currently provided as a response to the
"HL_INFO_HW_IDLE" IOCTL is merely a general boolean value.
This patch extends it and provides also a bitmask that indicates which
of the device engines are busy.
Signed-off-by: Tomer Tayar
---
drivers/misc/habanalabs/debugfs.c
Hi Gwendal,
One comment below
On 28/6/19 21:17, Gwendal Grignou wrote:
> Remove duplicate code in cros-ec-accel-legacy,
> use cros-ec-sensors-core functions and structures when possible.
>
> On glimmer, check the 2 accelerometers are presented and working.
>
> Signed-off-by: Gwendal Grignou
>
The patch updates the device idle check:
- Add reading the DMA core status register, because it is possible that
a QMAN has finished its work but the DMA itself is still running.
- Remove the MME shadow status check, as the MME ARCH status register
includes the status of all MME shadows.
Signe
Command submissions sent to the device are composed of command buffers
which are targeted to different device engines, like DMA and compute
entities. When a command submission gets stuck, knowing in which engine
the stuck is, is crucial for debugging.
This patch adds a debugfs node that exports thi
"git diff" says:
\ No newline at end of file
after modifying the files.
Signed-off-by: Geert Uytterhoeven
---
v2:
- Split patches per maintainer.
---
Documentation/ABI/testing/sysfs-power | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-
Hi,
On 6/25/19 7:27 PM, Aniket Masule wrote:
> Present core assignment is static. Introduced load balancing
> across the cores. Load on earch core is calculated and core
> with minimum load is assigned to given instance.
>
> Signed-off-by: Aniket Masule
> ---
> drivers/media/platform/qcom/venus
+++ Zhiqiang Liu [28/06/19 20:32 +0800]:
From: Zhiqiang Liu
Problem: Users can call ref_module func in their modules to construct
relationships with other modules. However, the holders
'/sys/module//holders' of the target module donot include
the users` module. So lsmod command misses detailed
"git diff" says:
\ No newline at end of file
after modifying the files.
Signed-off-by: Geert Uytterhoeven
---
v2:
- Split patches per maintainer.
---
Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/
On Mon, Jul 01, 2019 at 02:43:14PM +0200, Geert Uytterhoeven wrote:
> Hi Ted,
>
> Despite this fix having been applied upstream, the kernel prints from
> time to time:
>
> EXT4-fs (sda1): error count since last fsck: 5
> EXT4-fs (sda1): initial error at time 1557931133:
> ext4_get_branch
On 01-Jul 11:02, Peter Zijlstra wrote:
> On Wed, Jun 26, 2019 at 06:29:12PM -0700, subhra mazumdar wrote:
> > Hi,
> >
> > Resending this patchset, will be good to get some feedback. Any suggestions
> > that will make it more acceptable are welcome. We have been shipping this
> > with Unbreakable E
Hi Aniket,
On 6/25/19 7:27 PM, Aniket Masule wrote:
> Add and interface to calculate load per core. Also,
> add an interface to get maximum cores available with
> video. This interface is preparation for updating core
> selection.
>
> Signed-off-by: Aniket Masule
> ---
> drivers/media/platform/
On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> The t->rcu_read_unlock_special union's need_qs bit can be set by the
> scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> needed from the rcu_read_unlock path. When this help arrives however, we
> can
On Wed, Jun 26, 2019 at 10:36:28AM +0530, Viresh Kumar wrote:
> Hi,
>
> We try to find an idle CPU to run the next task, but in case we don't
> find an idle CPU it is better to pick a CPU which will run the task the
> soonest, for performance reason.
>
> A CPU which isn't idle but has only SCHED_
Interrupts are getting misrouted and/or dropped on SKLYLAKE_X based D-2100s
when C6 and SERIRQ are enabled. I've only seen this issue on systems
using SERIRQs (in my case for a LPC based UART providing the serial
console for a headless server).
One failure mode is "do_IRQ: 8.33 No irq handler for
401 - 500 of 816 matches
Mail list logo
