On Tue, 17 Jul 2018, Kirill A. Shutemov wrote:
> Per-KeyID direct mappings require changes into how we find the right
> virtual address for a page and virt-to-phys address translations.
>
> page_to_virt() definition overwrites default macros provided by
> . We only overwrite the macros if MTKME
Based on the documentation provided in AMD's Open-Source
Register Reference For AMD Family 17h Processors:
https://support.amd.com/TechDocs/56255_OSRR.pdf
I've added support for reading Cores and Package energy usage from AMD's
"RAPL" MSRs. In order to correctly detect the AMD processor
This fixes the reported family on modern AMD processors (e.g. Ryzen,
which is family 0x17). Previously these processors all showed up as
family 0xf.
See the document
https://support.amd.com/TechDocs/56255_OSRR.pdf
section CPUID_Fn0001_EAX for how to calculate the family
from the BaseFamily
Based on the Open-Source Register Reference for AMD Family 17h
Processors Models 00h-2Fh:
https://support.amd.com/TechDocs/56255_OSRR.pdf
These processors report RAPL support in bit 14 of CPUID 0x8007 EDX,
and the following MSRs are present:
0xc0010299 (RAPL_PWR_UNIT), like Intel's
On Mon, Jul 02, 2018 at 06:58:54PM -0400, Sinan Kaya wrote:
> pci_reset_bus() and pci_reset_slot() functions are not being used by
> any code. Remove them from the kernel in favor of pci_try_reset_bus()
> and pci_try_reset_slot() functions.
>
> Signed-off-by: Sinan Kaya
> ---
>
On Wed, Jul 18, 2018 at 02:03:18PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 12, 2018 at 01:29:40PM -0400, Johannes Weiner wrote:
> > + /* Time in which tasks wait for the CPU */
> > + state = PSI_NONE;
> > + if (tasks[NR_RUNNING] > 1)
> > + state = PSI_SOME;
> > +
On 7/18/2018 3:30 PM, Bjorn Helgaas wrote:
On Mon, Jul 02, 2018 at 06:58:54PM -0400, Sinan Kaya wrote:
pci_reset_bus() and pci_reset_slot() functions are not being used by
any code. Remove them from the kernel in favor of pci_try_reset_bus()
and pci_try_reset_slot() functions.
On 18:57-20180718, Tony Lindgren wrote:
> * Nishanth Menon [180718 18:08]:
> > On 16:26-20180626, Nishanth Menon wrote:
> > > Hi,
> > >
> > > This is an minor update from V1 posted earlier:
> > > https://marc.info/?l=linux-kernel=15294374542413
Linus,
Please pull a couple of DT fixes. Details below.
Rob
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
On Wed, Jul 18, 2018 at 2:27 PM David Howells wrote:
>
> As I may have said, I have tried modifying the kernel to pass the cred pointer
> down.
It should always be there in the 'struct file *'.
Now, we may have some broken stuff that passes only inodes down, but
they probably really should be
On Wed, 2018-07-18 at 13:50 -0600, Rob Herring wrote:
>
> > So Rob, I think that's precisely where the disconnect is.
> >
> > I think we all (well hopefully) agree that those few tunables don't fit
> > in any existing subystem and aren't likely to ever do (famous last
> > words...).
> >
> >
Hi There !
Is this email address correct?
Reply for important info .
Thank You
There is a potential execution path in which function
platform_get_resource() returns NULL. If this happens,
we will end up having a NULL pointer dereference.
Fix this by adding a sanity check in order to avoid a
NULL pointer dereference.
This code was detected with the help of Coccinelle.
Cc:
On Mon, Jul 16, 2018 at 09:06:51PM -0700, Andrey Smirnov wrote:
> Add support for Zodiac Inflight Innovations SSMB SPU3
> board (VF610-based).
>
> Cc: Shawn Guo
> Cc: Fabio Estevam
> Cc: cphe...@gmail.com
> Cc: linux-arm-ker...@lists.infradead.org
> Cc: devicet...@vger.kernel.org
> Cc:
On Wed, 2018-07-18 at 21:48 +0200, Krzysztof Kozlowski wrote:
> Three files dual-licensed were missing the SPDX license identifiers.
As mentioned before [1] I am in the process of preparing a patch set
which cleans that up across all Toradex device trees. Our plan is to
actually move them all to
On Wed, 18 Jul 2018 23:15:26 +0200
Miquel Raynal wrote:
> Hi Abhishek,
>
> Abhishek Sahu wrote on Fri, 6 Jul 2018
> 13:21:58 +0530:
>
> > Remove the NAND_SKIP_BBTSCAN to use RAM based BBT.
>
> Unless I am understanding it the wrong way, NAND_SKIP_BBTSCAN will skip
> the scan of the
Adjust tcp_client.py and tcp_server.py to work with Python 3 by using
the print function, marking string literals as bytes, and using the
newer exception syntax. This should be functionally equivalent and
support Python 2.6 through Python 3.7.
Signed-off-by: Jeremy Cline
---
On Tue, Jul 17, 2018 at 04:21:57PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 12, 2018 at 01:29:40PM -0400, Johannes Weiner wrote:
> > diff --git a/include/linux/sched/stat.h b/include/linux/sched/stat.h
> > index 04f1321d14c4..ac39435d1521 100644
> > --- a/include/linux/sched/stat.h
> > +++
On Wed, Jul 18, 2018 at 2:28 PM David Howells wrote:
>
> Are network filesystems allowed to use f_cred at I/O time to determine the
> authentication/encryption parameters to commune with the server?
Absolutely. file->f_cred is very much "what was my ID at open time".
Of course, you may well
On 19-07-18, 11:26, Shawn Guo wrote:
> On Thu, Jul 19, 2018 at 08:54:54AM +0530, Viresh Kumar wrote:
> > On 19-07-18, 11:20, Shawn Guo wrote:
> > > On Wed, Jul 18, 2018 at 02:54:49PM +0800, Anson Huang wrote:
> > > > Commit b97872d4eb22 ("ARM: dts: imx: Add missing OPP properties for
> > > >
Hi Linus, Al,
I'm thinking of adding in the attached patch as a starting point for replacing
write() as the method by which configuration/actioning is done.
For the moment, it just glues the key and the value back together inside the
kernel and passes that on to the filesystem. I'm still
Hi Abhishek,
Abhishek Sahu wrote on Fri, 6 Jul 2018
13:21:59 +0530:
> Driver does not send the commands to NAND device for page
> read/write operations in ->cmdfunc(). It just does some
> minor variable initialization and rest of the things
> are being done in actual ->read/write_oob[_raw].
Linus Torvalds wrote:
> I explained earlier why it's wrong and fragile, and why it can just
> cause the *reverse* security problem if you do it wrong. So now you
> take a subtle bug, and make it even more subtle, and encourage people
> to do this known-broken model of using creds at IO time.
Abhishek,
Miquel Raynal wrote on Wed, 18 Jul 2018
23:41:44 +0200:
> Hi Boris,
>
> Boris Brezillon wrote on Wed, 18 Jul 2018
> 23:36:37 +0200:
>
> > On Wed, 18 Jul 2018 23:15:26 +0200
> > Miquel Raynal wrote:
> >
> > > Hi Abhishek,
> > >
> > > Abhishek Sahu wrote on Fri, 6 Jul 2018
> >
On Wed, 18 Jul 2018 16:52:54 +0200 Geert Uytterhoeven
wrote:
> As PERL uses its own internal character encoding, always calling
> encode("utf8", ...) on the author name may cause corruption, leading to
> an author signoff mismatch.
>
> This happens in the following cases:
> - If a patch is
This patch adds the mechanic needed for user space to send PMU specific
configuration to the kernel driver using an ioctl() command. That way
events can keep track of options that don't fit in the perf_event_attr
structure like the selection of a CoreSight sink to use for the session.
Hi Bjorn,
Commits
27a6c9ebf29b ("PCI: v3-semi: Fix I/O space page leak")
db2aff16ea70 ("PCI: mediatek: Fix I/O space page leak")
52022fc6f6ad ("PCI: faraday: Fix I/O space page leak")
a9c0419ec92f ("PCI: aardvark: Fix I/O space page leak")
45cb32b4e8ea ("PCI: designware: Fix I/O space
Hi Arnd, Olof,
Please pull UniPhier SoC changes for the v4.19 MW.
Thanks!
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
On Wed, Jul 18, 2018 at 2:22 PM Al Viro wrote:
>
> Why is counter any better than LSB of a pointer?
Easier nesting, but if you do it with the "surround by a macro" model
I guess you can just save/restore instead (like you did in
call_with_creds).
Linus
Hi,
This patch series adds a driver and DT binding using the interconnect (ICC)
framework [1] to describe the Qualcomm SDM845 platform's topology of its
interconnected buses and internal aggregation nodes known as
Bus Clock Managers(BCM). The SDM845 ICC provider driver would aggregate and
satisfy
Add RSC(Resource State Coordinator) provider
dictating network-on-chip interconnect bus performance
found on SDM845-based platforms.
Signed-off-by: David Dai
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
Introduce Qualcomm SDM845 specific provider driver using the
interconnect framework.
Signed-off-by: David Dai
---
.../bindings/interconnect/qcom-sdm845.txt | 22 +
drivers/interconnect/qcom/Kconfig | 8 +
drivers/interconnect/qcom/Makefile | 1 +
On Wed, Jul 18, 2018 at 6:18 PM, kbuild test robot wrote:
> Hi Todd,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on staging/staging-testing]
> [also build test ERROR on next-20180718]
> [cannot apply to v4.18-rc5]
> [if your patch is
Sigh...
Nacked-by: Tetsuo Handa
because David is not aware what is wrong.
On 2018/07/19 5:22, David Rientjes wrote:
> On Wed, 18 Jul 2018, Tetsuo Handa wrote:
>
>>> diff --git a/mm/mmap.c b/mm/mmap.c
>>> --- a/mm/mmap.c
>>> +++ b/mm/mmap.c
>>> @@ -3059,25 +3059,28 @@ void exit_mmap(struct
On Wed, Jul 18, 2018 at 01:43:00PM -0700, Linus Torvalds wrote:
> What I really think I'd prefer is to have some simple way to "poison"
> current_cred(). It could be something as simple as a per-thread
> counter, and we'd have current_cred() do
>
> WARN_ON_ONCE(in_interrupt() ||
Adding a new IOCTL command to communicate PMU specific configuration to
PMU kernel drivers. This can be anything a PMU might need for
configuration that doesn't fit in the perf_event_attr structure, such
as the CoreSight sink to use for a session.
Signed-off-by: Mathieu Poirier
---
Using sysFS to communicate sink information for a trace session doesn't
work when more than one CPU is involved in the scenario. As such
communicate the sink information to each event by using the SET_DRV_CONFIG
ioctl command.
Signed-off-by: Mathieu Poirier
---
This set adds the capability to communiate event specific configuration
to the PMU kernel driver using an ioctl(). The functionatlity is made
generic enough for anyone to use but is targeted at the identification
of CoreSight sinks when operating in CPU-wide trace scenarios.
Applies cleanly on
Following in the footsteps of what was done for filters, adding the
necessary mechanic needed to push down driver specific configuration
to the kernel using an ioctl. By proceeding this way PMU specific
configuration such as CoreSight sink specification can be communicated
to each event.
This patch uses the PMU driver configuration held in event::hw::drv_config
to select a sink for each event that is created (the old sysFS way of
working is kept around for backward compatibility).
By proceeding in this way a sink can be used by multiple sessions
without having to play games with
Make structure perf_evsel available to the PMU driver configuration code.
That way function perf_evsel__apply_drv_config() can be used from within
that code and information pertaining to the 'perf_evsel_config_term' is
still available.
Signed-off-by: Mathieu Poirier
---
When pmu::setup_aux() is called the coresight PMU needs to know which
sink to use for the session by looking up the information in the
drv_config field of the hw_perf_event structure.
As such simply replace the cpu information by the complete perf_event
structure and change all affected
Hi Alan,
Thanks for your time, comments below
On Wednesday, July 18, 2018 9:47:24 PM CEST Alan Tull wrote:
> On Thu, Jun 28, 2018 at 2:50 AM, Federico Vaga
wrote:
> > On Wednesday, 27 June 2018 23:23:07 CEST Alan Tull wrote:
> >> On Wed, Jun 27, 2018 at 4:25 AM, Federico Vaga
> >
> > wrote:
On Wed, Jul 18, 2018 at 4:49 PM Stephen Rothwell wrote:
>
> Hi Bjorn,
>
> Commits
>
> 27a6c9ebf29b ("PCI: v3-semi: Fix I/O space page leak")
> db2aff16ea70 ("PCI: mediatek: Fix I/O space page leak")
> 52022fc6f6ad ("PCI: faraday: Fix I/O space page leak")
> a9c0419ec92f ("PCI: aardvark:
On Tue, Jul 17, 2018 at 05:01:42PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 12, 2018 at 01:29:40PM -0400, Johannes Weiner wrote:
> > +static bool psi_update_stats(struct psi_group *group)
> > +{
> > + u64 some[NR_PSI_RESOURCES] = { 0, };
> > + u64 full[NR_PSI_RESOURCES] = { 0, };
> > +
2018-07-14 0:30 GMT+09:00 Olof Johansson :
> Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
> in particular. So, probe for whether it's available and use the previous
> (linux) targets if it isn't.
>
> Reported-by: Laura Abbott
> Cc: Paul Kocialkowski
> Signed-off-by: Olof
On Tue, Jul 17, 2018 at 05:59:27PM -0400, Waiman Long wrote:
> On a VM with only 1 vCPU, the locking fast path will always be
> successful. In this case, there is no need to use the the PV qspinlock
> code which has higher overhead on the unlock side than the native
> qspinlock code.
Why not make
David Howells writes:
> Andy Lutomirski wrote:
>
>> > Also you can't currently directly create a bind mount from userspace as you
>> > can only bind from another path point - which you may not be able to access
>> > (either by permission failure or because it's not in your mount namespace).
>>
On Thu, Jul 19, 2018 at 02:32:06AM +0200, Frederic Weisbecker wrote:
> On Wed, Jul 11, 2018 at 06:03:42PM +0100, David Woodhouse wrote:
> > On Wed, 2018-07-11 at 09:49 -0700, Paul E. McKenney wrote:
> > > And here is an updated v4.15 patch with Marius's Reported-by and David's
> > > fix to my lost
On 2018-07-19 01:14, Bjorn Helgaas wrote:
This is a v3 of Oza's patches [1]. It's available at [2] if you prefer
git.
v3 changes:
- Add pci_aer_clear_fatal_status() to clear ERR_FATAL bits, only
called
from pcie_do_fatal_recovery(). Moved to first in series to avoid a
window where
Hi Mathieu,
On 07/18/2018 08:43 PM, Mathieu Poirier wrote:
When enabling the lockdep mechanic and working with CPU-wide scenarios we
get the following console output:
This is fixed by working with the cpu_present_mask, avoinding at the same
the need to use get/put_online_cpus() that
On Fri, 6 Jul 2018 13:21:59 +0530
Abhishek Sahu wrote:
> Driver does not send the commands to NAND device for page
> read/write operations in ->cmdfunc(). It just does some
> minor variable initialization and rest of the things
> are being done in actual ->read/write_oob[_raw].
>
> The generic
[+cc Mike (hfi1)]
On Mon, Jul 16, 2018 at 10:28:35PM +, alex_gagn...@dellteam.com wrote:
> On 7/16/2018 4:17 PM, Bjorn Helgaas wrote:
> >> ...
> >> The easiest way to detect this is with pcie_print_link_status(),
> >> since the bottleneck is usually the link that is downtrained. It's not
> >>
On Tue, Jul 17, 2018 at 12:03:47PM +0200, Peter Zijlstra wrote:
> This is still a scary amount of accounting; not to mention you'll be
> adding O(cgroup-depth) to this in a later patch.
>
> Where are the performance numbers for all this?
I benchmarked it using our two most scheduling sensitive
Hi Jiri,
As far as I know, once you go into annotate mode, via perf report TUI
mode, the percentage you see per instruction is relative to the
function. I would like the option to display the total percentage,
i..e, the importance of the instruction for the entire run. Right now,
if I want that,
On Wed, 2018-07-18 at 14:42 -0700, Andrew Morton wrote:
> On Wed, 18 Jul 2018 16:52:54 +0200 Geert Uytterhoeven
> wrote:
>
> > As PERL uses its own internal character encoding, always calling
> > encode("utf8", ...) on the author name may cause corruption, leading to
> > an author signoff
On 07/18/2018 02:22 PM, Jacek Anaszewski wrote:
On 07/18/2018 08:54 PM, Jacek Anaszewski wrote:
On 07/18/2018 09:56 AM, Pavel Machek wrote:
Hi!
I believe I meant "changing patterns from kernel in response to events
is probably overkill"... or something like that.
Anyway -- to clean up the
Hi Andrey,
On Tue, Jul 17, 2018 at 1:06 AM, Andrey Smirnov
wrote:
> +/dts-v1/;
> +#include "vf610.dtsi"
> +
> +/ {
> + model = "ZII VF610 SSMB SPU3 Board";
> + compatible = "zii,vf610spu3", "zii,vf610dev", "fsl,vf610";
Looks good to me.
Just a minor comment: Is " "zii,vf610dev"
2018-07-12 23:05 GMT+09:00 Kirill A. Shutemov :
> On Thu, Jul 12, 2018 at 05:01:30PM +0900, Masahiro Yamada wrote:
>>
>> This series renames LDFLAGS to KBUILD_LDFLAGS
>> after some Makefile cleanups.
>>
>> Currently, the last patch does not apply to Linus' tree
>> due to missing pre-requisite
> --- a/arch/x86/mm/mktme.c
> +++ b/arch/x86/mm/mktme.c
> @@ -1,3 +1,4 @@
> +#include
> #include
>
> phys_addr_t mktme_keyid_mask;
> @@ -37,3 +38,14 @@ struct page_ext_operations page_mktme_ops = {
> .need = need_page_mktme,
> .init = init_page_mktme,
> };
> +
> +int
On 2018-07-18 11:04, Douglas Anderson wrote:
Add both the interface and core clock.
Signed-off-by: Douglas Anderson
---
drivers/clk/qcom/gcc-sdm845.c | 73 +++
1 file changed, 73 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm845.c
On 14 July 2018 at 00:30, Olof Johansson wrote:
> Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
> in particular. So, probe for whether it's available and use the previous
> (linux) targets if it isn't.
>
> Reported-by: Laura Abbott
> Cc: Paul Kocialkowski
>
On Wed, Jul 11, 2018 at 06:03:42PM +0100, David Woodhouse wrote:
> On Wed, 2018-07-11 at 09:49 -0700, Paul E. McKenney wrote:
> > And here is an updated v4.15 patch with Marius's Reported-by and David's
> > fix to my lost exclamation point.
>
> Thanks. Are you sending the original version of that
Thanks, we will run the test with your patch, will update the test results in
24 Hours.
Current status is:
We can reproduce the issue in 3000 cycles stress S/R test, we can't reproduce
the kernel panic with our patch in 6000 cycles.
-Original Message-
From: Takashi Iwai
Sent:
On 18-07-18, 16:34, Wei Xu wrote:
> Hi Viresh,
>
> On 2018/7/5 6:09, Viresh Kumar wrote:
> > Hi,
> >
> > This is an attempt to fix the broken or partially defined DT bindings
> > for cooling-maps. We should list every device that participates in
> > cooling down at a certain trip point, instead
On Wed, 2018-07-18 at 21:48 +0200, Krzysztof Kozlowski wrote:
> Fix indentation and alignment when spaces were used instead of tabs.
> This fixes checkpatch errors like:
>
> ERROR: code indent should use tabs where possible
> #306: FILE: arch/arm/boot/dts/tegra20-paz00.dts:306:
>
Do you have need for image editing?
We have 20 image editors and on daily basis 2000 images can be processed.
If you want to check our quality of work please send us a photo with
instruction and we will work on it.
Photo cut out, masking, clipping path Color, brightness and contrast
correction
On Wed, 2018-07-18 at 21:48 +0200, Krzysztof Kozlowski wrote:
> Fix incorrect format used for OR clause in SPDX license identifier.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> arch/arm/boot/dts/tegra124-apalis-v1.2-eval.dts | 2 +-
> arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 2 +-
>
On Wed, Jun 6, 2018 at 1:02 PM Richard Guy Briggs wrote:
> Signed-off-by: Richard Guy Briggs
> ---
> net/rfkill/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I would suggest splitting this patch from the audit container ID
patchset and sending it to the netdev folks. It
On Wed, Jul 18, 2018 at 12:24 PM, Bo Chen wrote:
> In 'e1000_set_ringparam()', the tx_ring and rx_ring are updated with new value
> and the old tx/rx rings are freed only when the device is up. There are
> resource
> leaks on old tx/rx rings when the device is not up. This bug is reported by
>
Boris,
Can you please check the change in qcom_nandc_write_oob() is
valid? I think it is but as this is a bit of a hack I prefer double checking.
Thanks,
Miquèl
Abhishek Sahu wrote on Fri, 6 Jul 2018
13:21:56 +0530:
> The NAND base layer calls write_oob() by setting bytes at
>
Hi!
> >Please keep in mind that this is ABI documentation for the pattern file
> >to be exposed by LED core, and not by the pattern trigger, that, as we
> >agreed, will be implemented later. In this case, I'd go for
>
> Gosh, I got completely distracted by the recent discussion about
> pattern
Hello Mylène,
On Wed, Jul 18, 2018 at 08:27:17PM +0200, Mylène Josserand wrote:
> Add the support of regulator to use it as VCC source.
>
> Signed-off-by: Mylène Josserand
> ---
> .../bindings/input/touchscreen/edt-ft5x06.txt | 1 +
> drivers/input/touchscreen/edt-ft5x06.c |
From: Omar Sandoval
There's a theoretical race condition that will cause /proc/kcore to miss
a memory hotplug event:
CPU0 CPU1
// hotplug event 1
kcore_need_update = 1
open_kcore() open_kcore()
kcore_update_ram()
From: Omar Sandoval
Currently, the ELF file header, program headers, and note segment are
allocated all at once, in some icky code dating back to 2.3. Programs
tend to read the file header, then the program headers, then the note
segment, all separately, so this is a waste of effort. It's
From: Omar Sandoval
Now that we're using an rwsem, we can hold it during the entirety of
read_kcore() and have a common return path. This is preparation for the
next change.
Signed-off-by: Omar Sandoval
---
fs/proc/kcore.c | 70 -
1 file
From: Omar Sandoval
The memory hotplug notifier kcore_callback() only needs kclist_lock to
prevent races with __kcore_update_ram(), but we can easily eliminate
that race by using an atomic xchg() in __kcore_update_ram(). This is
preparation for converting kclist_lock to an rwsem.
Signed-off-by:
From: Omar Sandoval
The vmcoreinfo information is useful for runtime debugging tools, not
just for crash dumps. A lot of this information can be determined by
other means, but this is much more convenient, and it only adds a page
at most to the file.
Signed-off-by: Omar Sandoval
---
From: Omar Sandoval
Now we only need kclist_lock from user context and at fs init time, and
the following changes need to sleep while holding the kclist_lock.
Signed-off-by: Omar Sandoval
---
fs/proc/kcore.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff
From: Omar Sandoval
The current code does a full search of the segment list every time for
every page. This is wasteful, since it's almost certain that the next
page will be in the same segment. Instead, check if the previous segment
covers the current page before doing the list search.
2018-07-19 2:15 GMT+09:00 Major Hayden :
> Copy the architecture-specific compressed kernel image to the
> directory used to make the tar package.
>
> Signed-off-by: Major Hayden
> ---
Thanks for the patch,
but I applied Olof's one, which copy more files.
On 07/17/2018 04:20 AM, Kirill A. Shutemov wrote:
> arch/x86/include/asm/mktme.h | 8 +
> arch/x86/mm/init_64.c| 10 +
> arch/x86/mm/mktme.c | 437 +++
> 3 files changed, 455 insertions(+)
I'm not the maintainer. But, NAK from me on this on
Dear Greg,
This is extcon-next pull request for v4.19. I add detailed description of
this pull request on below. Please pull extcon with following updates.
Best Regards,
Chanwoo Choi
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17
On Wed, Jul 18, 2018 at 3:50 PM Fabio Estevam wrote:
>
> Hi Andrey,
>
> On Tue, Jul 17, 2018 at 1:06 AM, Andrey Smirnov
> wrote:
>
> > +/dts-v1/;
> > +#include "vf610.dtsi"
> > +
> > +/ {
> > + model = "ZII VF610 SSMB SPU3 Board";
> > + compatible = "zii,vf610spu3", "zii,vf610dev",
Hi Andrey,
On Wed, Jul 18, 2018 at 9:51 PM, Andrey Smirnov
wrote:
> It's not used in Linux, but I do rely on it in Barebox here:
>
> https://git.pengutronix.de/cgit/barebox/tree/arch/arm/boards/zii-vf610-dev/board.c#n94
>
> and here:
>
>
On Thu, 19 Jul 2018, at 04:37, Rob Herring wrote:
> On Tue, Jul 17, 2018 at 5:28 PM Andrew Jeffery wrote:
> >
> > On Tue, 17 Jul 2018, at 14:26, Benjamin Herrenschmidt wrote:
> > > On Mon, 2018-07-16 at 07:55 -0600, Rob Herring wrote:
> > > > If that data is one set per SoC, then i'm not that
On Wed, Jul 18, 2018 at 2:10 PM, Laura Abbott wrote:
>
> Implementation of stackleak based heavily on the x86 version
>
> Signed-off-by: Laura Abbott
> ---
> Since last time: Minor style cleanups. Re-wrote check_alloca to
> correctly handle all stack types. While doing that, I also realized
>
On Tue, Jul 17, 2018 at 02:55:24PM +0530, Jagan Teki wrote:
> This patch adds parallel display support for i.MX6DL Mamoj board
> along with relevant backlight through pwm.
>
> LCD power sequence is added by 'Michael Trimarchi'.
>
> Signed-off-by: Simone CIANNI
> Signed-off-by: Raffaele
Arguments of 'pin' subcommand should be checked
at the very beginning of do_pin_any().
Otherwise segfault errors can occur when using
'map pin' or 'prog pin' commands, so fix it.
# bpftool prog pin id
Segmentation fault
Fixes: 71bb428fe2c1 ("tools: bpf: add bpftool")
Reviewed-by: Jakub
In preparation for enabling the stackleak plugin on arm64,
we need a way to get the bounds of the current stack.
Introduce a new primitive current_stack_type which is similar
to x86's get_stack_info. Utilize that to rework
on_accessible_stack slightly as well.
Signed-off-by: Laura Abbott
---
Hi,
This is the new version of stackleak for arm64 to go with v14 of the
series for x86. I have a cover letter and few more cc's to go along with
some of the prep work.
I also apologize for terrible versioning on these series. Usually I try
to just reply to the top level patch with this addition
On 18/07/2018 20:03, Jim Mattson wrote:
> On Wed, Jul 18, 2018 at 10:55 AM, Radim Krčmář wrote:
>
>>> + vmx->nested.nested_run_pending = 1;
>> This is not necessary. We're only copying state and do not add anything
>> that would be lost on a nested VM exit without prior VM entry.
> If
Implementation of stackleak based heavily on the x86 version
Signed-off-by: Laura Abbott
---
Since last time: Minor style cleanups. Re-wrote check_alloca to
correctly handle all stack types. While doing that, I also realized
current_top_of_stack was incorrect so I fixed that as well.
---
Hi Boris,
Boris Brezillon wrote on Wed, 18 Jul 2018
23:36:37 +0200:
> On Wed, 18 Jul 2018 23:15:26 +0200
> Miquel Raynal wrote:
>
> > Hi Abhishek,
> >
> > Abhishek Sahu wrote on Fri, 6 Jul 2018
> > 13:21:58 +0530:
> >
> > > Remove the NAND_SKIP_BBTSCAN to use RAM based BBT.
> >
> >
I asked about this before and it still isn't covered in the description:
You were specifically asked (maybe in person at LSF/MM?) not to modify
allocator to pass the keyid around. Please specifically mention how
this design addresses that feedback in the patch description.
You were told, "don't
Introduces three new helper functions:
* munmap_addr_sanity()
* munmap_lookup_vma()
* munmap_mlock_vma()
They will be used by do_munmap() and the new do_munmap with zapping
large mapping early in the later patch.
There is no functional change, just code refactor.
Signed-off-by: Yang Shi
Background:
Recently, when we ran some vm scalability tests on machines with large memory,
we ran into a couple of mmap_sem scalability issues when unmapping large memory
space, please refer to https://lkml.org/lkml/2017/12/14/733 and
https://lkml.org/lkml/2018/2/20/576.
History:
Then akpm
When running some mmap/munmap scalability tests with large memory (i.e.
> 300GB), the below hung task issue may happen occasionally.
INFO: task ps:14018 blocked for more than 120 seconds.
Tainted: GE 4.9.79-009.ali3000.alios7.x86_64 #1
"echo 0 >
The description doesn't mention the potential performance implications
of this patch. That's criminal at this point.
> --- a/arch/x86/mm/mktme.c
> +++ b/arch/x86/mm/mktme.c
> @@ -1,4 +1,5 @@
> #include
> +#include
> #include
>
> phys_addr_t mktme_keyid_mask;
> @@ -49,3 +50,51 @@ int
There is a potential execution path in which function
platform_get_resource() returns NULL. If this happens,
we will end up having a NULL pointer dereference.
Fix this by adding asanity check in order to avoid a
NULL pointer dereference.
This code was detected with the help of Coccinelle.
Cc:
1 - 100 of 1452 matches
Mail list logo
