On 7/24/2020 12:43 PM, pet...@infradead.org wrote:
On Fri, Jul 24, 2020 at 04:59:34PM +0200, Peter Zijlstra wrote:
On Fri, Jul 24, 2020 at 07:46:32AM -0700, Andi Kleen wrote:
Something that seems to 'work' is:
'{cycles,cpu/instructions,period=5/}', so maybe you can make the
group modifie
On 7/24/20 7:52 PM, Stanimir Varbanov wrote:
> Hi Lina,
>
> On 7/24/20 7:28 PM, Lina Iyer wrote:
>> On Fri, Jul 24 2020 at 03:03 -0600, Rajendra Nayak wrote:
>>> Hi Maulik/Lina,
>>>
>>> On 7/23/2020 11:36 PM, Stanimir Varbanov wrote:
Hi Rajendra,
After applying 2,3 and 4/5 patche
Currently nouveau relies on being able to use the
drm_connector_helper_funcs->mode_valid() hook within
drm_connector_helper_funcs->get_modes() so that we can ignore invalid
modes when figuring out the connector's native mode. Since we're about
to add a ->mode_valid_ctx() hook for MST, we'll also ne
While we already check whether a given atomic state can fit in the
available bandwidth for an MST topology, we don't currently bother to
prune display modes on MST connectors if said modes are impossible to
fit on the MST link irregardless of the current display state.
So, let's avoid reporting im
On 28.12.18 12:52, Greg Kroah-Hartman wrote:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit 68239654acafe6aad5a3c1dc7237e60accfebc03 upstream.
The sequence
fpu->initialized = 1; /* step A *
Hi Shaik,
On Tue, Jul 21, 2020 at 04:16:21PM +0530, Shaik Sajida Bhanu wrote:
> From: Pradeep P V K
>
> Add the bandwidth domain supporting performance state and
> the corresponding OPP tables for the sdhc device on sc7180.
>
> Signed-off-by: Pradeep P V K
> Signed-off-by: Shaik Sajida Bhanu
On Fri, 24 Jul 2020 09:46:06 -0700
"Andres Beltran" wrote:
> Assignments to buffer_actual_len and requestid happen before packetlen
> is checked to be within buflen. If this condition is true,
> hv_ringbuffer_read() returns with these variables already set to some
> value even though no data is a
Hi Thierry,
Applied, thanks for the fix!
On 24/07/2020 19:01, Thierry Reding wrote:
> From: Thierry Reding
>
> When a thermal zone is looked up by an ID and no zone is found matching
> that ID, the thermal_zone_get_by_id() function will return a pointer to
> the thermal zone list head which is
On Fri, Jul 24, 2020 at 12:35:28PM -0400, Steven Rostedt wrote:
> On Fri, 24 Jul 2020 18:19:21 +0200
> Oscar Carter wrote:
>
> > > The linker trick is far less intrusive, and I believe less error prone.
> >
> > If we use the linker trick, the warning -Wcast-function-type dissapears,
> > but in a w
Hi Andy Shevchenko,
Thanks for the review.
Accepted comments will address in V3 and Added few comments in inline.
> -Original Message-
> From: Andy Shevchenko
> Sent: Thursday, July 23, 2020 11:33 PM
> To: Srinivas Neeli
> Cc: Linus Walleij ; Bartosz Golaszewski
> ; Michal Simek ;
> Sh
The current ELF loading mechancism provides page-aligned mappings. This
can lead to the program being loaded in a way unsuitable for
file-backed, transparent huge pages when handling PIE executables.
Tested: verified program with -Wl,-z,max-page-size=0x20 loading
Signed-off-by: Chris Kennelly
The current ELF loading mechancism provides page-aligned mappings. This
can lead to the program being loaded in a way unsuitable for
file-backed, transparent huge pages when handling PIE executables.
While specifying -z,max-page-size=0x20 to the linker will generate
suitably aligned segments
Hi Jon,
I like how RST can help make for a better grouping of our documents
and put it into other formats. But I have to rant a little because I'm
currently experiencing some of the frustration that Peter commonly
complains about.
I'm looking into how to make the event directory tree be created o
From: Qiuxu Zhuo
A PCIe Root Complex Event Collector(RCEC) has the base class 0x08,
sub-class 0x07, and programming interface 0x00. Add the class code
0x0807 to identify RCEC devices and add the defines for the RCEC
Endpoint Association Extended Capability.
See PCI Express Base Specification, ve
Root Complex Event Collectors (RCEC) provide support for terminating error
and PME messages from Root Complex Integrated Endpoints (RCiEPs). An RCEC
resides on a Bus in the Root Complex. Multiple RCECs can in fact reside on
a single bus. An RCEC will explicitly declare supported RCiEPs through the
From: Jonathan Cameron
Currently the kernel does not handle AER errors for Root Complex integrated
End Points (RCiEPs)[0]. These devices sit on a root bus within the Root Complex
(RC). AER handling is performed by a Root Complex Event Collector (RCEC) [1]
which is a effectively a type of RCiEP on
The Root Complex Event Collectors(RCEC) appear as peers to Root Ports
and also have the AER capability. So add RCEC support to the current AER
service driver and attach the AER service driver to the RCEC device.
Co-developed-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
On Wed, Jul 22, 2020 at 2:34 PM Max Filippov wrote:
>
> vmlinux.bin and vmlinux.bin.gz are always rebuilt in the kernel build
> process. Add them to 'targets' and move them to the boot subdirectory
> where their rules are. Update make rules that refer to them.
>
> Signed-off-by: Max Filippov
> --
From: Qiuxu Zhuo
When an RCEC device signals error(s) to a CPU core, the CPU core
needs to walk all the RCiEPs associated with that RCEC to check
errors. So add the function pcie_walk_rcec() to walk all RCiEPs
associated with the RCEC device.
Co-developed-by: Sean V Kelley
Signed-off-by: Qiuxu
From: Qiuxu Zhuo
When attempting error recovery for an RCiEP associated with an RCEC device,
there needs to be a way to update the Root Error Status, the Uncorrectable
Error Status and the Uncorrectable Error Severity of the parent RCEC.
So add the 'rcec' field to the pci_dev structure and provid
The Root Complex Event Collectors(RCEC) appear as peers of Root Ports
and also have the PME capability. So add RCEC support to the current PME
service driver and attach the PME service driver to the RCEC device.
Co-developed-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
From: Qiuxu Zhuo
The Root Complex Event Collectors(RCEC) appear as peers to Root Ports
and also have the AER capability. So add RCEC support to the current AER
error injection driver.
Co-developed-by: Sean V Kelley
Signed-off-by: Qiuxu Zhuo
Signed-off-by: Sean V Kelley
---
drivers/pci/pcie/a
From: Qiuxu Zhuo
If a Root Complex Integrated Endpoint (RCiEP) is implemented, errors may
optionally be sent to a corresponding Root Complex Event Collector (RCEC).
Each RCiEP must be associated with no more than one RCEC. Interface errors
are reported to the OS by RCECs.
For an RCEC (technicall
From: Qiuxu Zhuo
Attempt to do function level reset for an RCiEP associated with an
RCEC device on fatal error.
Signed-off-by: Qiuxu Zhuo
---
drivers/pci/pcie/err.c | 31 ++-
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git a/drivers/pci/pcie/err.c b/dri
On Wed, Jul 22, 2020 at 2:34 PM Max Filippov wrote:
>
> uImage and xipImage are always rebuilt in the xtensa kernel build
> process. Add them to 'targets' to avoid that.
>
> Signed-off-by: Max Filippov
> ---
Reviewed-by: Masahiro Yamada
> arch/xtensa/boot/Makefile | 1 +
> 1 file changed, 1
On Thu, Jul 23, 2020 at 10:15:17PM +0200, Thomas Gleixner wrote:
> Thomas Gleixner writes:
>
> > Ira Weiny writes:
> >> On Fri, Jul 17, 2020 at 12:06:10PM +0200, Peter Zijlstra wrote:
> >>> On Fri, Jul 17, 2020 at 12:20:56AM -0700, ira.we...@intel.com wrote:
> >> I've been really digging into th
Hi,
On Fri, 17 Jul 2020 18:00:02 +0200
Thomas Gleixner wrote:
> Setting interrupt affinity on inactive interrupts is inconsistent when
> hierarchical irq domains are enabled. The core code should just store the
> affinity and not call into the irq chip driver for inactive interrupts
> because th
Hi Steven,
On Fri, Jul 24, 2020 at 07:14:18PM +0200, Oscar Carter wrote:
> On Fri, Jul 24, 2020 at 12:35:28PM -0400, Steven Rostedt wrote:
> > On Fri, 24 Jul 2020 18:19:21 +0200
> > Oscar Carter wrote:
> >
> > > > The linker trick is far less intrusive, and I believe less error prone.
> > >
> > >
On Sat, Jul 18, 2020 at 3:39 PM Masahiro Yamada wrote:
>
> Constify arrays as well as strings.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild.
> scripts/kconfig/images.c | 30 +++---
> scripts/kconfig/images.h | 30 +++---
> 2
This patch adds helper functions which are used in the NVMeOF configfs
when the user is configuring the passthru subsystem. Here we ensure
that only one subsys is assigned to each nvme_ctrl by using an xarray
on the cntlid.
The subsystem's version number is overridden by the passed through
control
Separate the code to obtain command effects from the code
to start a passthru request and move the nvme_passthru_start() and
nvme_passthru_end() functions up above nvme_submit_user_cmd() in order
that they may be used in a new helper a subsequent patch.
The new helper function will be necessary fo
This is v16 of the passthru patchset which make a bunch of cleanup as
suggested by Christoph.
I attempted to change the connect_q to a passthru_q (one of the
suggestions) but doing so did not allow for the removal of the need
for the namespace structure. The ns structure is needed to obtain
comman
Add passthru command handling capability for the NVMeOF target and
export passthru APIs which are used to integrate passthru
code with nvmet-core.
The new file passthru.c handles passthru cmd parsing and execution.
In the passthru mode, we create a block layer request from the nvmet
request and ma
When CONFIG_NVME_TARGET_PASSTHRU as 'passthru' directory will
be added to each subsystem. The directory is similar to a namespace
and has two attributes: device_path and enable. The user must set the
path to the nvme controller's char device and write '1' to enable the
subsystem to use passthru.
A
nvme_find_get_ns() and nvme_put_ns() are required by the target passthru
code and are exported under the NVME_TARGET_PASSTHRU namespace.
Based-on-a-patch-by: Chaitanya Kulkarni
Signed-off-by: Logan Gunthorpe
---
drivers/nvme/host/core.c | 6 --
drivers/nvme/host/nvme.h | 2 ++
2 files chang
From: Chaitanya Kulkarni
This patch updates KConfig file for the NVMeOF target where we add new
option so that user can selectively enable/disable passthru code.
Signed-off-by: Chaitanya Kulkarni
[log...@deltatee.com: fixed some of the wording in the help message]
Signed-off-by: Logan Gunthorpe
The host driver should decide whether to use SGLs or PRPs and they
currently assume the flags are cleared after the call to
nvme_setup_cmd(). However, passed-through commands may erroneously
set these bits; so clear them for all cases.
Signed-off-by: Logan Gunthorpe
Reviewed-by: Sagi Grimberg
--
nvme_ctrl_get_by_path() is analogous to blkdev_get_by_path() except it
gets a struct nvme_ctrl from the path to its char dev (/dev/nvme0).
It makes use of filp_open() to open the file and uses the private
data to obtain a pointer to the struct nvme_ctrl. If the fops of the
file do not match, -EINVA
Introduce a new nvme_execute_passthru_rq() helper which calls
nvme_passthru_[start|end]() around blk_execute_rq(). This ensures
all passthru calls (including nvme_submit_io()) will be wrapped
appropriately.
nvme_execute_passthru_rq() will also be useful for the nvmet passthru
code and is exported
On Wed, 24 Jun 2020 01:33:16 -0700, Andrei Vagin wrote:
> Currently the vdso has no awareness of time namespaces, which may
> apply distinct offsets to processes in different namespaces. To handle
> this within the vdso, we'll need to expose a per-namespace data page.
>
> As a preparatory step, th
> On Jul 24, 2020, at 10:23 AM, Ira Weiny wrote:
>
> On Thu, Jul 23, 2020 at 10:15:17PM +0200, Thomas Gleixner wrote:
>> Thomas Gleixner writes:
>>
>>> Ira Weiny writes:
On Fri, Jul 17, 2020 at 12:06:10PM +0200, Peter Zijlstra wrote:
>> On Fri, Jul 17, 2020 at 12:20:56AM -0700, ira
On Fri, Jul 24, 2020 at 8:24 AM Oleg Nesterov wrote:
>
> not sure this makes any sense, but this looks like another user of
> trylock_page_bit_common(), see the patch below on top of 1/2.
Ok, that makes sense. Except you did it on top of the original patch
without the fix to set WQ_FLAG_WOKEN for
On Fri, 24 Jul 2020 13:22:00 -0400
Steven Rostedt wrote:
> > It is tempting to describe the second kind as starting with a
> > component, but that isn't always accurate: a pathname can lack both
> > slashes and components, it can be empty, in other words. This is
> > generally forbidden in POSIX
On Fri, Jul 24, 2020 at 09:45:18AM +0200, Paul Menzel wrote:
> Am 24.07.20 um 00:32 schrieb Kees Cook:
> > On Thu, Jul 23, 2020 at 09:10:15PM +, Mazin Rezk wrote:
> As Linux 5.8-rc7 is going to be released this Sunday, I wonder, if commit
> 3202fa62f ("slub: relocate freelist pointer to middle
commit 8171cd68806b ("KVM: x86: use raw clock values consistently")
causes KVM to accidentally write seconds to the nanoseconds field (and
vice versa) in the KVM wall clock. Fix it by reversing this accidental
switch. Modulo the written nanoseconds value by NSEC_PER_SEC to correct
for the amount of
On Fri, 24 Jul 2020 19:14:18 +0200
Oscar Carter wrote:
> > The linker trick should only affect architectures that don't implement
> > the needed features. I can make it so the linker trick is only applied
> > to those archs, and other archs that want more protection only need to
> > add these fea
On Fri, Jul 24, 2020 at 04:48:36PM +0200, Sedat Dilek wrote:
> On Fri, Jul 24, 2020 at 4:30 PM Arvind Sankar wrote:
> >
> > On Fri, Jul 24, 2020 at 02:50:34AM +0200, Sedat Dilek wrote:
> > > On Thu, Jul 23, 2020 at 9:30 PM Nick Terrell
> > > wrote:
> > > >
> > > > From: Nick Terrell
> > > >
> >
From: Jordan Hand
Fix improper line breaks and format all example yavta and media-ctl
commands as code blocks to improve readability.
Signed-off-by: Jordan Hand
---
v2:
- Lined up options in hanging indents
- Removed extra newlines
- Broke up long lines in v4l2n command, added backslashes
Do
On Fri, 24 Jul 2020 13:36:56 -0400
Steven Rostedt wrote:
> Which BTW, is supported by the following architectures:
>
> arm
> arm64
> csky
> parisc
> powerpc
> riscv
> s390
> x86
And here's a list of architectures that have function tracing but need
to be updated:
ia64
micro
On 7/24/20 3:50 AM, Codrin Ciubotariu wrote:
> The MACB embeds an MDIO bus controller. For this reason, the PHY nodes
> were represented as sub-nodes in the MACB node. Generally, the
> Ethernet controller is different than the MDIO controller, so the PHYs
> are probed by a separate MDIO driver. Sin
On Fri, Jul 24, 2020 at 06:02:52PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Load the GDT right after switching to virtual addresses to make sure
> there is a defined GDT for exception handling.
>
> Signed-off-by: Joerg Roedel
Reviewed-by: Kees Cook
--
Kees Cook
On Fri, Jul 24, 2020 at 01:22:00PM -0400, Steven Rostedt wrote:
> I like how RST can help make for a better grouping of our documents
> and put it into other formats. But I have to rant a little because I'm
> currently experiencing some of the frustration that Peter commonly
> complains about.
Tha
On 7/24/20 3:03 AM, Muchun Song wrote:
> In the reservation routine, we only check whether the cpuset meets
> the memory allocation requirements. But we ignore the mempolicy of
> MPOL_BIND case. If someone mmap hugetlb succeeds, but the subsequent
> memory allocation may fail due to mempolicy restr
On Fri, Jul 24, 2020 at 06:02:51PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> When stack-protector is enabled a valid GS_BASE is needed before
> calling any C code function, because the stack canary is loaded from
> per-cpu data.
>
> Signed-off-by: Joerg Roedel
Reviewed-by: Kees Cook
On Fri, Jul 24, 2020 at 06:02:54PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Make sure there is a stack once the kernel runs from virual addresses.
> At this stage any secondary CPU which boots will have lost its stack
> because the kernel switched to a new page-table which does not map
On Fri, Jul 24, 2020 at 06:02:53PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Make sure segments are properly set up before setting up an IDT and
> doing anything that might cause a #VC exception. This is later needed
> for early exception handling.
>
> Signed-off-by: Joerg Roedel
Rev
Hi,
On Wed, Jul 22, 2020 at 6:01 PM Stephen Boyd wrote:
>
> The busy loop in rpmh_rsc_send_data() is written with the assumption
> that the udelay will be preempted by the tcs_tx_done() irq handler when
> the TCS slots are all full. This doesn't hold true when the calling
> thread is an irqthread
On Fri, Jul 24, 2020 at 06:02:32PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The x86-64 ABI defines a red-zone on the stack:
>
> The 128-byte area beyond the location pointed to by %rsp is considered
> to be reserved and shall not be modified by signal or interrupt
> handlers. Th
On Fri, Jul 24, 2020 at 07:07:06PM +0200, Jan Kiszka wrote:
> On 28.12.18 12:52, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Sebastian Andrzej Siewior
> >
> > commit 68239654acafe6aad5a3c1dc72
From: David Collins
Add support for TEMP_ALARM GEN2 PMIC peripherals with digital
major revision 1. This revision utilizes a different temperature
threshold mapping than earlier revisions.
Signed-off-by: David Collins
Signed-off-by: Guru Das Srinagesh
---
drivers/thermal/qcom/qcom-spmi-temp-
From: Veera Vegivada
Currently driver is suppressing the negative temperature
readings from the vadc. Consumers of the thermal zones need
to read the negative temperature too. Don't suppress the
readings.
Signed-off-by: Veera Vegivada
Signed-off-by: Guru Das Srinagesh
---
drivers/thermal/qcom
Hi Linus,
Things remain quiet here, a few more of the usual fixes.
The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:
Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags
On Fri, 24 Jul 2020 13:40:20 -0400
Steven Rostedt wrote:
> On Fri, 24 Jul 2020 13:36:56 -0400
> Steven Rostedt wrote:
>
> > Which BTW, is supported by the following architectures:
> > x86
Ah, you can lose support on x86 if you don't enable DYNAMIC_FTRACE,
which is stupid to do. I only en
> -Original Message-
> From: Stephen Hemminger
> Sent: Friday, July 24, 2020 1:11 PM
> To: Andres Beltran
> Cc: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger ;
> wei@kernel.org; linux-hyp...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Michael Kelley ;
> parri.and...@gma
Hello Greg,
(Re-sending again this pull request)
This is habanalabs pull request for the merge window of kernel 5.9. It
contains many small improvements to common and GAUDI code. Details are in
the tag.
Thanks,
Oded
The following changes since commit 92ca3dd4867bafbfd026b06d53737d61ded1bd27:
On Fri, Jul 24, 2020 at 06:02:55PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Also move it to a header file so that it can be used in the idt code
> to setup the early IDT.
>
> Signed-off-by: Joerg Roedel
Reviewed-by: Kees Cook
--
Kees Cook
On Fri, Jul 24, 2020 at 06:03:00PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Refactor the message printed to the kernel log which indicates whether
> SEV or SME is active to print a list of enabled encryption features.
> This will scale better in the future when more memory encryption
>
On Fri, Jul 24, 2020 at 06:02:59PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Add the sev_es_active function for checking whether SEV-ES is enabled.
> Also cache the value of MSR_AMD64_SEV at boot to speed up the feature
> checking in the running code.
>
> Signed-off-by: Joerg Roedel
On Fri, Jul 24, 2020 at 01:40:20PM -0400, Steven Rostedt wrote:
> On Fri, 24 Jul 2020 13:36:56 -0400
> Steven Rostedt wrote:
>
> > Which BTW, is supported by the following architectures:
> >
> > arm
> > arm64
> > csky
> > parisc
> > powerpc
> > riscv
> > s390
> > x86
>
> And here's
On Thu, Jul 23, 2020 at 10:11:28PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 23, 2020 at 08:41:03PM +0100, Chris Wilson wrote:
>
> > I am very sorry for the wild goose chase.
>
> *phew*... all good then. I was starting to go a little ga-ga trying to
> make sense of things.
>
> Arguably we shoul
On Fri, Jul 24, 2020 at 06:03:36PM +0200, Joerg Roedel wrote:
> From: Martin Radev
>
> Make sure the machine supports RDRAND, otherwise there is no trusted
> source of of randomness in the system.
>
> To also check this in the pre-decompression stage, make has_cpuflag
> not depend on CONFIG_RAND
On Fri, Jul 24, 2020 at 06:03:32PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> For SEV-ES this entry point will be used for restarting APs after they
> have been offlined. Remove the '0' from the name to reflect that.
>
> Signed-off-by: Joerg Roedel
Reviewed-by: Kees Cook
--
Kees Co
On 7/24/20 8:28 AM, Dinghao Liu wrote:
The variable authmode will keep uninitialized if neither if
statements used to initialize this variable are not triggered.
Besides Greg's comment, you need to re-parse this sentence. I realize that
English is probably not your first language, but this one
On Fri, Jul 24, 2020 at 06:03:31PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The APs are not ready to handle exceptions when verify_cpu() is called
> in secondary_startup_64.
>
> Signed-off-by: Joerg Roedel
Thanks for updating this! :)
Reviewed-by: Kees Cook
--
Kees Cook
On Fri, Jul 24, 2020 at 06:02:32PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The x86-64 ABI defines a red-zone on the stack:
>
> The 128-byte area beyond the location pointed to by %rsp is considered
> to be reserved and shall not be modified by signal or interrupt
> handlers. Th
On Wed, Jul 22, 2020 at 05:01:51PM +0200, Peter Zijlstra wrote:
> Get rid of the __call_single_node union and cleanup the API a little
> to avoid external code relying on the structure layout as much.
>
> Signed-off-by: Peter Zijlstra (Intel)
Tested-by: Paul E. McKenney
> ---
> arch/mips/kern
The devlink device name is of the form "supplier:consumer". But ":" is
fairly common in device names and makes it visually hard to distinguish
supplier and consumer. So, replace it with "--" to make it easier.
Signed-off-by: Saravana Kannan
---
Documentation/ABI/testing/sysfs-class-devlink | 2 +
Document scope of the mutex used by driver.
Signed-off-by: Krzysztof Kozlowski
---
It seems mutex was introduced to protect:
1. setting actual frequency/voltage,
2. dmc->curr_rate (in exynos5_dmc_get_cur_freq()).
However dmc->curr_rate in exynos5_dmc_get_status() is not protected. Is
it a bug?
On Fri, Jul 24, 2020 at 07:44:37PM +0200, Greg Kroah-Hartman wrote:
On Fri, Jul 24, 2020 at 07:07:06PM +0200, Jan Kiszka wrote:
On 28.12.18 12:52, Greg Kroah-Hartman wrote:
> 4.9-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Sebastian An
Use the new SSR notifier infrastructure to request notifications of
modem events, rather than the remoteproc IPA notification system.
The latter was put in place temporarily with the knowledge that the
new mechanism would become available.
Signed-off-by: Alex Elder
---
David: If you approve, ple
The IPA code now uses the generic remoteproc SSR notification
mechanism. This makes the original IPA notification code unused
and unnecessary, so get rid of it.
This is effectively a revert of commit d7f5f3c89c1a ("remoteproc:
add IPA notification to q6v5 driver").
Signed-off-by: Alex Elder
---
The IPA driver needs to be notified about changes to the state of
the modem (starting, shutting down, etc.). A notification mechanism
was put in place for that purpose, but a more general system has now
been accepted:
https://lore.kernel.org/linux-remoteproc/1592965408-16908-1-git-send-email-ri
On Fri, Jul 24, 2020 at 7:45 AM Andi Kleen wrote:
>
> On Fri, Jul 24, 2020 at 12:19:59AM -0700, Ian Rogers wrote:
> > for_each_set_bit, or similar functions like for_each_cpu, may be hot
> > within the kernel. If many bits were set then one could imagine on
> > Intel a "bt" instruction with every
On Fri, Jul 24, 2020 at 06:41:30PM +0100, Matthew Wilcox wrote:
> I think we're all pretty comfortable seeing function names adorned with
> a closing pair of parens. The ``...`` to adorn constants feels OK to me,
> but maybe not to you? If that feels excessive, can you suggest something
> that wo
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to 5fff09bc141570cd15c118b097b17dec832b
On Thu, Jul 23, 2020 at 03:50:57PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 23, 2020 at 03:55:56PM +0200, Peter Zijlstra wrote:
[ . . . ]
> > > + ts2 = sched_clock();
> > > + ts_delta = ts2 - *ts1;
> > > + if (likely(ts_delta <= CSD_LOCK_TIMEOUT)) {
> > > + cpu_relax();
> > > +
Hi,
I have few other cleanups which I could take. Two patches need here testing as
they are not trivial.
Best regards,
Krzysztof
Add blank lines to improve code readability. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/bt1-l2-ctl.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/memory/bt1-l2-ctl.c b/drivers/memory/bt1-l2-ctl.c
index 633fea6a4edf..85965fa26e0b 100644
--- a/dri
On 7/23/20 01:43, Kalle Valo wrote:
> "Gustavo A. R. Silva" writes:
>
>> Friendly ping: who can take this? :)
>
> I'll take this if it's ok. I have been just busy due to vacation period.
>
Thanks, Kalle. :)
--
Gustavo
Use proper kerneldoc to fix GCC warnings like:
drivers/memory/omap-gpmc.c:299: warning: Function parameter or member 'cs'
not described in 'gpmc_get_clk_period'
drivers/memory/omap-gpmc.c:432: warning: Excess function parameter 'ma'
description in 'get_gpmc_timing_reg'
Signed-off-by: Kr
The line continuation contained spaces but still failed to properly
align with open parenthesis.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/mvebu-devbus.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/
Add missing braces to all arms of if statement to align with coding
convention.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/mvebu-devbus.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/memory/mvebu-devbus.c b/drivers/memory/mvebu-devbus.c
index 886ae
Fix arbitary -> arbitrary.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/omap-gpmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 414bfb481266..76a9c700cbd5 100644
--- a/drivers/memory/omap-gpmc.c
+++ b/
On Fri, Jun 19, 2020 at 05:17:47PM -0700, Matthew Wilcox wrote:
> On Fri, Jun 19, 2020 at 05:17:50PM -0400, Qian Cai wrote:
> > Running a syscall fuzzer by a normal user could trigger this,
> >
> > [55649.32][T515839] WARNING: CPU: 6 PID: 515839 at
> > fs/iomap/direct-io.c:391 iomap_dio_actor
Driver uses 'unsigned int' in other places instead of 'unsigned'.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/omap-gpmc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 62577255ba0f..e4d2f359bcfa 100
Since driver tracks reserved memory, freeing a non-reserved GPMC should
not be fatal and crash the system. Printing a warning is friendlier.
Signed-off-by: Krzysztof Kozlowski
---
Not tested on HW.
---
drivers/memory/omap-gpmc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --
On Fri, Jul 24, 2020 at 07:16:44PM +0100, Al Viro wrote:
Argh... Sorry, hit send too early; the missing summary would be
Max Filippov has caught a breakage introduced in xtensa this
cycle by the csum_and_copy_..._user() series. Cut'n'paste from the
wrong source - the check that belongs
The driver already uses 'if (!res)' pattern in the probe function so be
consistent.
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/omap-gpmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 76a9c700cbd5..ce
Add separate entry for Broadcom STB DPFE driver, selected by platforms
by default. This allows further customization and compile testing.
Signed-off-by: Krzysztof Kozlowski
---
I have other changes around drivers/memory/Kconfig pending. Sending them
together would avoid conflicts.
---
arch/ar
Use proper kerneldoc to fix GCC warnings like:
drivers/memory/of_memory.c:30: warning: Function parameter or member 'dev'
not described in 'of_get_min_tck'
Signed-off-by: Krzysztof Kozlowski
---
drivers/memory/of_memory.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
1001 - 1100 of 1414 matches
Mail list logo
