On 08/23/2017 08:47 AM, Vlastimil Babka wrote:
> On 07/24/2017 02:38 PM, Michal Hocko wrote:
>>
>> Do we need to duplicated a part of __set_page_owner? Can we pull out
>> both owner and handle out __set_page_owner?
>
> I wanted to avoid overhead in __set_page_owner() by introducing extra
> shared
This code is no longer used, the logging function was changed by commit
fbca164776e4 ("net: stmmac: Use the right logging functi"). It was
previously showing information about the type if the IRQ, if it's polled,
ignored or a normal interrupt. As we don't want information loss, I have
moved this co
Hello,
On 08/24/2017 07:38 AM, Takashi Sakamoto wrote:
On Aug 23 2017 23:51, Oleksandr Grytsov wrote:
Hi,
Thank you for detailed explanation.
We understand that emulated interrupt on the frontend side is
completely not
acceptable and definitely we need to provide some feedback mechanism
fro
> -Original Message-
> From: A.s. Dong
> Sent: Wednesday, July 26, 2017 10:57 AM
> To: A.s. Dong; linux-...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> sb...@codeaurora.org; mturque...@baylibre.com; donga...@gmail.com;
> shawn...@kernel.org; A
Hi Will,
On 23/08/2017 18:42, Will Deacon wrote:
> Hi Eric,
>
> On Wed, Aug 23, 2017 at 02:36:53PM +0200, Auger Eric wrote:
>> On 23/08/2017 12:25, Will Deacon wrote:
>>> On Tue, Aug 22, 2017 at 10:09:15PM +0300, Michael S. Tsirkin wrote:
On Fri, Aug 18, 2017 at 05:49:42AM +0300, Michael S.
On Thu, 24 Aug 2017 00:49:34 +0200,
Colin King wrote:
>
> From: Colin Ian King
>
> Trivial fix to spelling mistake in MODULE_PARM_DESC text
>
> Signed-off-by: Colin Ian King
The OSS code is already dead (kconfig disabled) and going to be
removed sooner or later, so let's leave as is.
thanks
On Thu, 24 Aug 2017 08:25:28 +0200,
Arvind Yadav wrote:
>
> snd_ac97_res_table are not supposed to change at runtime. All functions
> working with snd_ac97_res_table provided by work with
> const snd_ac97_res_table. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Applie
From: Joonsoo Kim
page_zone_id() is a specialized function to compare the zone for the pages
that are within the section range. If the section of the pages are
different, page_zone_id() can be different even if their zone is the same.
This wrong usage doesn't cause any actual problem since
__munl
From: Bjorn Andersson
Renaming the glink_rpm_xx functions and structs to qcom_glink_xx
equivalents helps to reuse the core glink protocol while adding
support for smem based glink transport in the later patches.
Signed-off-by: Bjorn Andersson
Signed-off-by: Sricharan R
---
drivers/rpmsg/qcom_
The glink protocol works with a shared-memory(transport) for
communication between the local and remote processors. The
existing glink-rpm driver implements the basic features
of the protocol and uses msgram as the transport.
The same is extended to support smem based transport as well.
The first
Currently if we receive a command that we still do not
support, then its simply discarded. While doing so, the
RX FIFO pointer also needs to be incremented. Fixing this.
Signed-off-by: Sricharan R
---
drivers/rpmsg/qcom_glink_native.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/r
Hi John,
On Wed, Aug 23, 2017 at 2:52 PM, John Garry wrote:
> On 22/08/2017 05:21, Ganapatrao Kulkarni wrote:
>>
>> Hi Arnaldo, Will,
>>
>> are there any comments on this series?
>>
>
> Hi Ganapatrao,
>
> Is it possible to have vendor sub-folder in tools/perf/pmu-events/arch/arm64
> folder (like
From: Bjorn Andersson
To fully read the received rx data from FIFO both the
command and data has to be read. Currently we read
command, data separately and process them. By adding
an offset parameter to RX FIFO peak accessor, command
and data can be read together, simplifying things.
So introduce
Once the remote side sends a rx done ack, check
for the intent reuse information from it and
suitably discard or reuse the remote passed
intent buffers.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_glink_native.c | 42 +++
From: Bjorn Andersson
Glink protocol requires that each message is aligned
on a 8 byte offset. This is purely a restriction
from glink, so in order to support clients which
do not adher to this, allow data packets of any size,
but align the head index accordingly, effectively
removing the alignme
The channel members lcids, rcids synchronised using
the idr_lock is accessed in both atomic/non-atomic
contexts. The readers are not currently synchronised.
That no correct, so add the readers as well under the
lock and use a spinlock.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
--
Just like we allocating and sending intent ids to remote,
remote side allocates and sends us the intents as well.
So save the intent ids and use it later while sending
data targeting the appropriate intents based on the size.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
---
drivers
Send RX data receive ack to remote and also inform
that local intent buffer is used and freed. This
informs the remote to request for next set of
intent buffers before doing a send operation.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_glink_native.c | 83 ++
While sending data, we search for suitable sized
intent to map and simply fail if a intent is not
found. Instead request for a intent of required
size and wait till one is alloted.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_glink_native.c | 76 +
Preallocate local intent buffers and pass the intent ids
to the remote. This way there are some default intents
available for the remote to start sending data without
having to wait by sending intent requests. Do this by
adding the rpmsg announce_create ops, which gets called
right after the rpmsg
While sending data, use the remote intent id buffer
of suitable size that was passed by remote previously.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_glink_native.c | 35 +--
1 file changed, 33 insertions(+), 2 deletions(-)
Intents are nothing but pre-allocated buffers of
appropriate size that are allocated on the local
side and communicated to the remote side and the
remote stores the list of intent ids that it is
informed.
Later when remote side is intenting to send data,
it picks up a right intent (based on the si
So previously on request from remote side, we allocated local
intent buffers and passed the ids to the remote. Now when
we receive data buffers from remote directed to that intent
id, copy the data to the corresponding preallocated intent
buffer.
Signed-off-by: Sricharan R
Signed-off-by: Bjorn An
G-link supports a version number and feature flags for each transport.
A combination of the version number and feature flags enable/disable:
(*) G-Link software updates for each edge
(*) Individual features for each edge
Endpoints negotiate both the version and the supported flags when
the tran
mbox_request_channel is done in probe, so free the
channel in remove.
Signed-off-by: Sricharan R
---
drivers/rpmsg/qcom_glink_native.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rpmsg/qcom_glink_native.c
b/drivers/rpmsg/qcom_glink_native.c
index 94b79e8..21adde3 100644
--- a/dr
From: Bjorn Andersson
The glink protocol supports different types of
transports (shared memory). With the core protocol
remaining the same, the way the transport's memory is
probed and accessed is different. So add support for
glink's smem based transports.
Adding a new smem transport register f
The TX FIFO can be full, if the remote client has
not read enough data (or) reading it slowly. So its
nessecary to return -EAGAIN to the local client to
enable retry.
Signed-off-by: Sricharan R
---
drivers/rpmsg/qcom_glink_native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
From: Bjorn Andersson
There is quite some code common in glink_rpm_probe that
can reused for glink-smem based transport as well. So
split the function and move the code to glink_native_probe
that can be used later when we add the support for
glink-smem based transport. Also reuse driver's remove
From: Bjorn Andersson
Move the common part of glink core protocol implementation to
glink_native.c that can be shared with the smem based glink
transport in the later patches.
Signed-off-by: Bjorn Andersson
Signed-off-by: Sricharan R
---
drivers/rpmsg/Kconfig |6 +-
drivers/rp
From: Bjorn Andersson
With the intention of reusing the glink core protocol commands
and code across both rpm and smem based transports, the only thing
different is way of accessing the shared-memory of the transport
(FIFO). So put the fifo accessor's of the transport's pipe (rx/tx)
behind indire
This patch set introduces Receive Side Scaling for the DPAA Ethernet
driver. Documentation is updated with details related to the new
feature and limitations that apply.
Added also a small fix.
v2: removed a C++ style comment
v3: move struct fman to header file to avoid exporting a function
Iorda
Add a block of 128 Rx frame queues per port. The FMan hardware will
send traffic on one of these queues based on the FMan port Parse
Classify Distribute setup. The hash computed by the FMan Keygen
block will select the Rx FQ.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/d
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
b/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
index 73ca8d7..4225806 100644
--- a/drivers/net/ethernet/freescal
Signed-off-by: Madalin Bucur
---
Documentation/networking/dpaa.txt | 68 ++-
1 file changed, 67 insertions(+), 1 deletion(-)
diff --git a/Documentation/networking/dpaa.txt
b/Documentation/networking/dpaa.txt
index 76e016d..f88194f 100644
--- a/Documentation/n
Set the skb hash when then FMan Keygen hash result is available.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 23 +++---
drivers/net/ethernet/freescale/dpaa/dpaa_eth.h | 1 +
drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c | 9 +++
From: Iordache Florinel-R70177
Add support for the FMan Keygen with a hardcoded scheme to spread
incoming traffic on a FQ range based on source and destination IPs
and ports.
Signed-off-by: Iordache Florinel
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/fman/Makefile |
Allow ethtool control of the Rx flow hashing. By default RSS is
enabled, this allows to turn it off by bypassing the FMan Keygen
block and sending all traffic on the default Rx frame queue.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c | 113
On Thu, Aug 24, 2017 at 11:02:36AM +0900, Byungchul Park wrote:
> On Wed, Aug 23, 2017 at 12:20:48PM +0200, Peter Zijlstra wrote:
> > On Wed, Aug 23, 2017 at 11:12:17AM +0900, Byungchul Park wrote:
> >
> > > > > We have to detect dependecies if it exists, even in the following
> > > > > case:
> >
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/fman/fman.c | 74 --
drivers/net/ethernet/freescale/fman/fman.h | 73 +
2 files changed, 73 insertions(+), 74 deletions(-)
diff --git a/drivers/net/ethernet/freescale/fman/fman
There is code duplicated over all architecture's headers for
futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr,
and comparison of the result.
Remove this duplication and leave up to the arches only the needed
assembly which is now in arch_futex_atomic_op_inuser.
This effective
efi_pe_entry body is somehow squashed into startup_32. In the old days,
we forced startup_32 to start at offset 0x00 and efi_pe_entry to start
at 0x10. But this requirement was removed in 99f857db8857 ("x86, build:
Dynamically find entry points in compressed startup code") long time
ago.
The way i
efi_pe_entry body is somehow squashed into startup_64. In the old days,
we forced startup_64 to start at offset 0x200 and efi_pe_entry to start
at 0x210. But this requirement was removed in 99f857db8857 ("x86, build:
Dynamically find entry points in compressed startup code") long time
ago.
The way
On Mon, Aug 14, 2017 at 09:52:15PM -0400, Zi Yan wrote:
> From: Zi Yan
>
> For THP soft-offline support, we first try to migrate a THP without
> splitting. If the migration fails, we split the THP and migrate the
> raw error page.
>
> migrate_pages() does not split a THP if the migration reason
On Thu, Aug 24, 2017 at 03:11:53PM +0900, Byungchul Park wrote:
> On Wed, Aug 23, 2017 at 07:47:14PM +0200, Peter Zijlstra wrote:
> > Those are fine and are indeed the flush_work() vs work inversion.
> >
> > The two straight forward annotations are:
> >
> > flush_work(work)process_one_work(wq
On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote:
> On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote:
> > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote:
> >
> > > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote:
> > > > Not all devices with ACPI and this combination of
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
fs/ocfs2/dlm/dlmrecovery.c: In function 'dlm_free_dead_locks':
fs/ocfs2/dlm/dlmrecovery.c:2306:6: warning: unused variable 'i'
[-Wunused-variable]
int i;
^
fs/ocfs2/dlm
The commit ("iommu/mediatek: Enlarge the validate PA range
for 4GB mode") introduce the following build error:
drivers/iommu/mtk_iommu.c: In function 'mtk_iommu_hw_init':
>> drivers/iommu/mtk_iommu.c:536:30: error: 'const struct mtk_iommu_data'
has no member named 'm4u_type'; did you mean 'm4u
The commit ("iommu/mediatek: Enlarge the validate PA range
for 4GB mode") introduce the following build warning while ARCH=arm:
drivers/iommu/mtk_iommu.c: In function 'mtk_iommu_iova_to_phys':
include/linux/bitops.h:6:24: warning: left shift count >= width
of type [-Wshift-count-overflow]
2017-08-23 20:22 GMT+08:00 Paolo Bonzini :
> On 22/08/2017 00:32, Adam Borowski wrote:
>> On Mon, Aug 21, 2017 at 09:58:34PM +0200, Radim Krčmář wrote:
>>> 2017-08-21 21:12+0200, Adam Borowski:
On Mon, Aug 21, 2017 at 09:26:57AM +0800, Wanpeng Li wrote:
> 2017-08-21 7:13 GMT+08:00 Adam Bor
(Adding Dave so that he is also aware of this)
Stephen Rothwell writes:
> As expetced, today's linux-next merge of the wireless-drivers-next tree
> got a conflict in:
>
> drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
>
> between commit:
>
> 92b0f7b26b31 ("iwlwifi: split the regulatory r
On 18/08/17 08:19, Vijay Viswanath wrote:
> From: Subhash Jadavani
>
> SDCC controller reset (SW_RST) during probe may trigger power irq if
> previous status of PWRCTL was either BUS_ON or IO_HIGH_V. So before we
> enable the power irq interrupt in GIC (by registering the interrupt
> handler), we
From: Arnd Bergmann
Casting between an 'int' and a pointer causes a warning on
64-bit architectures in compile-testing this driver:
drivers/phy/ralink/phy-ralink-usb.c: In function 'ralink_usb_phy_probe':
drivers/phy/ralink/phy-ralink-usb.c:195:13: error: cast from pointer to
integer of differen
On 18/08/17 08:19, Vijay Viswanath wrote:
> From: Sahitya Tummala
>
> There is a rare scenario in HW, where the first clear pulse could
> be lost when the actual reset and clear/read of status register
> are happening at the same time. Fix this by retrying upto 10 times
> to ensure the status reg
Greg,
On Thursday 24 August 2017 05:00 AM, Greg Kroah-Hartman wrote:
> On Wed, Aug 23, 2017 at 07:50:46PM +0530, Kishon Vijay Abraham I wrote:
>> Greg,
>>
>> On Wednesday 23 August 2017 07:09 PM, Arnd Bergmann wrote:
>>> Casting between an 'int' and a pointer causes a warning on
>>> 64-bit archite
I've been running linux on Intel cherry-trail devices and discovered that I
couldn't get into S4. Debugging I found that the system would hang if I
attempted to hotplug a CPU (as is done in the final UP to SMP transition in
S4).
The simplest repro was:
echo 0 > /sys/devices/system/cpu/cpu1/onlin
* Jeffrey Hugo wrote:
> > > This commit has been exposed to 0day test robot and -next testing
> > > and is available in the git repository at:
> > >
> > >git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> > > for-mingo
> > >
> > > for you to fetch changes up to a58163d8
On Wed, 23 Aug 2017 13:47:13 -0600
Mathieu Poirier wrote:
> >> This is a renewed attempt at fixing a problem reported by Steve Rostedt [1]
> >> where DL bandwidth accounting is not recomputed after CPUset and CPUhotplug
> >> operations. When CPUhotplug and some CUPset manipulation take place root
On Wed, Aug 23, 2017 at 04:54:43PM -0600, Toshi Kani wrote:
> ACPI OEM ID / OEM Table ID / Revision can be used to identify
> a platform based on ACPI firmware info. acpi_blacklisted(),
> intel_pstate_platform_pwr_mgmt_exists(), and some other funcs,
> have been using similar check to detect a lis
On Wed, Aug 23, 2017 at 10:46:42PM +0200, Rafael J. Wysocki wrote:
> I can expose a branch with this series for you to merge if that helps.
I think that'll be the best solution. So yes, pls lemme know when you
have it so that I can pick up the rest.
Thx.
--
Regards/Gruss,
Boris.
Good maili
On Mon, Aug 21, 2017 at 6:03 PM, Dmitry Fleytman wrote:
> Commit e0429362ab15
> ("usb: Add device quirk for Logitech HD Pro Webcams C920 and C930e")
> introduced quirk to workaround an issue with some Logitech webcams.
>
> Apparently model C920-C has the same issue so applying
> the same quirk as
On 23/08/2017 18:02, Paolo Bonzini wrote:
>
> More duct tape would have been just:
>
> - if (pvclock_gtod_data.clock.vclock_mode != VCLOCK_TSC)
> + mode = READ_ONCE(pvclock_gtod_data.clock.vclock_mode);
> + if (mode != VCLOCK_TSC &&
> + (mode != VCLOCK_PVCLOCK || !pvclock_nest
+ some OMAP folks and Linux OMAP list
On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
> Hclk is the MCAN's interface clock. However, for OMAP based devices such as
> DRA7 SoC family the interface clock is handled by hwmod. Therefore, this
> interface clock is managed by hwmod driver via p
Stephen,
On Thursday 24 August 2017 10:53 AM, Stephen Rothwell wrote:
> Hi Greg,
>
> On Tue, 22 Aug 2017 15:07:33 +1000 Stephen Rothwell
> wrote:
>>
>> Hi Kishon,
>>
>> After merging the phy-next tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> drivers/phy/ra
Hi Liyang,
On 08/24/17 at 11:54am, Dou Liyang wrote:
> > > Test in my own PC(Lenovo M4340).
> > > Ask help for doing regression testing for the bug said in commit
> > > c4e1acbb35e4
> > > ("ACPI / init: Invoke early ACPI initialization later").
> > >
> >
> > Now, I can prove this patch doesn't r
ALIGN+GLOBAL is effectively what ENTRY does, so use ENTRY which is
dedicated for exactly this purpose -- global functions.
Note that stub32_clone is a C-like leaf function -- it has a standard
call frame -- it only switches one argument and continues by jumping
into C. And since each ENTRY should
Functions in math-emu are annotated as ENTRY, but their ends are not
annotated at all. But these are standard functions called from C, with
proper stack register update etc.
Omitting the ends means:
* the annotations are not paired and we cannot deal with such functions
e.g. in objtool
* the sym
在 2017-08-22 21:39，Andrew Lunn 写道：
On Tue, Aug 22, 2017 at 12:03:59PM +0800, Icenowy Zheng wrote:
From: Icenowy Zheng
Some RTL8211E chips have broken GbE function, which needs a hack to
fix. It's said that this fix will affect the performance on not-buggy
PHYs, so it should only be enabled on
On Thu, Aug 24, 2017 at 04:37:13PM +0900, Byungchul Park wrote:
> On Thu, Aug 24, 2017 at 03:11:53PM +0900, Byungchul Park wrote:
> > On Wed, Aug 23, 2017 at 07:47:14PM +0200, Peter Zijlstra wrote:
> > > Those are fine and are indeed the flush_work() vs work inversion.
> > >
> > > The two straight
Hi,
this is the revised patch set to add the support for Dollar Cove TI
PMIC found on some Intel Cherry Trail laptops / tablets. All drivers
are based on the original code from Intel downstream patches, with
lots of rewrites and cleanups. MFD driver is implemented as a
stand-alone like a few oth
On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote:
> On 08/23/2017 12:49 AM, Maxime Ripard wrote:
> > Hi Florian,
> >
> > On Tue, Aug 22, 2017 at 11:35:01AM -0700, Florian Fainelli wrote:
> > So I think what you are saying is either impossible or engineering-wise
> > a very
On Thu, Aug 03, 2017 at 04:12:31PM -0600, Tyler Baicar wrote:
> Currently we acknowledge errors before clearing the error status.
> This could cause a new error to be populated by firmware in-between
> the error acknowledgment and the error status clearing which would
> cause the second error's sta
This patch adds the opregion driver for Dollar Cove TI PMIC on Intel
Cherry Trail devices. The patch is based on the original work by
Intel, found at:
https://github.com/01org/ProductionKernelQuilts
with many cleanups and rewrites.
The driver is currently provided only as built-in to follow
This provides a new input driver for supporting the power button on
Dollar Cove TI PMIC, found on Cherrytrail-based devices.
The patch is based on the original work by Intel, found at:
https://github.com/01org/ProductionKernelQuilts
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=193891
Si
This patch adds the MFD driver for Dollar Cove TI PMIC (ACPI INT33F5)
that is found on some Intel Cherry Trail devices.
The driver is based on the original work by Intel, found at:
https://github.com/01org/ProductionKernelQuilts
This is a minimal version for adding the basic resources. Currentl
This is the initial attempt of implementing kexec_file_load() support
on arm64.[1]
Most of the code is based on kexec-tools (along with some kernel code
from x86 and from powerpc, which also came from kexec-tools).
This patch series enables us to
* load the kernel, either Image or vmlinux, with
The first PT_LOAD segment, which is assumed to be "text" code, in vmlinux
will be loaded at the offset of TEXT_OFFSET from the begining of system
memory. The other PT_LOAD segments are placed relative to the first one.
Regarding kernel verification, since there is no standard way to contain
a sign
From: Thiago Jung Bauermann
IMA will use the module_signature format for append signatures, so export
the relevant definitions and factor out the code which verifies that the
appended signature trailer is valid.
Also, create a CONFIG_MODULE_SIG_FORMAT option so that IMA can select it
and be able
message[] field won't be part of the definition of mz header.
This change is crucial for enabling kexec_file_load on arm64 because
arm64's "Image" binary, as in PE format, doesn't have any data for it and
accordingly the following check in pefile_parse_binary() will fail:
chkaddr(cursor,
This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., from higher to lower.
It will be used in kexec_file implementati
Commit-ID: d74be47673676eded2f0bb8274e752bed32c42d8
Gitweb: http://git.kernel.org/tip/d74be47673676eded2f0bb8274e752bed32c42d8
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:16 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 11:51:28 -0300
perf xyarray: Sa
build_elf_exec_info() can also be useful for other architectures,
including arm64. So let it factored out.
Signed-off-by: AKASHI Takahiro
Cc: Michael Ellerman
Cc: Thiago Jung Bauermann
Cc: Dave Young
Cc: Vivek Goyal
Cc: Baoquan He
---
arch/Kconfig | 3 +
arch/powerpc
The "Image" binary will be loaded at the offset of TEXT_OFFSET from
the start of system memory. TEXT_OFFSET is basically determined from
the header of the image.
Regarding kernel verification, it will be done through
verify_pefile_signature() as arm64's "Image" binary can be seen as
in PE format.
Commit-ID: 475fb533fb7d3dcf009a434f9b9ea238b93f4cb8
Gitweb: http://git.kernel.org/tip/475fb533fb7d3dcf009a434f9b9ea238b93f4cb8
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:17 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 11:51:31 -0300
perf evsel: Fix
In contrast to kexec_add_buffer(), this function assumes that kbuf->mem
is already assigned by caller. This type of allocation is commonly used
in kexec-tools.
This function will be used on arm64 in loading vmlinux(elf) binary.
Signed-off-by: AKASHI Takahiro
Cc: Dave Young
Cc: Vivek Goyal
Cc:
prepare_elf_headers() can also be useful for other architectures,
including arm64. So let it factored out.
Signed-off-by: AKASHI Takahiro
Cc: Dave Young
Cc: Vivek Goyal
Cc: Baoquan He
---
arch/x86/kernel/crash.c | 324 --
include/linux/kexec.h |
Commit-ID: de5077c4e38f2a51f50d28bdd5e4a0f14b3d16ff
Gitweb: http://git.kernel.org/tip/de5077c4e38f2a51f50d28bdd5e4a0f14b3d16ff
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:22 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 12:09:04 -0300
perf tools: Add
Modify arm64/Kconfig and Makefile to enable kexec_file_load support.
Signed-off-by: AKASHI Takahiro
Cc: Catalin Marinas
Cc: Will Deacon
---
arch/arm64/Kconfig | 22 ++
arch/arm64/kernel/Makefile | 2 +-
2 files changed, 23 insertions(+), 1 deletion(-)
diff --git a
On Wed, Aug 23, 2017 at 09:31:53AM -0700, Florian Fainelli wrote:
> On 08/23/2017 12:49 AM, Maxime Ripard wrote:
> > Hi Florian,
> >
> > On Tue, Aug 22, 2017 at 11:35:01AM -0700, Florian Fainelli wrote:
> > So I think what you are saying is either impossible or engineering-wise
> > a very
Commit-ID: 77d0871c76bad1093a3d86870fe76dd1ad0ca397
Gitweb: http://git.kernel.org/tip/77d0871c76bad1093a3d86870fe76dd1ad0ca397
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:19 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 11:56:22 -0300
perf bpf: Tighte
Commit-ID: d73bad06851b8d5745c11dd4ab789464f6c71b39
Gitweb: http://git.kernel.org/tip/d73bad06851b8d5745c11dd4ab789464f6c71b39
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:23 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 12:15:53 -0300
perf tools: Expr
Commit-ID: 8d3db2b97f5cb22cc589ba1e8e5232a26bfeb5d6
Gitweb: http://git.kernel.org/tip/8d3db2b97f5cb22cc589ba1e8e5232a26bfeb5d6
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:24 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 12:19:05 -0300
perf tools: Incr
On Wed, Aug 23, 2017 at 08:59:00AM -0700, Andi Kleen wrote:
> > so if I find HITM with this flag set I should count it
> > as remote HITM then? something like attached.. untested
>
> You mean for c2c? Yes looks reasonable.
yes, it seems to fix c2c to find remote HITMs again
on skylake.. I'll post
Commit-ID: d66dccdb13c9748f27d8401b45c027953fc833e8
Gitweb: http://git.kernel.org/tip/d66dccdb13c9748f27d8401b45c027953fc833e8
Author: Andi Kleen
AuthorDate: Fri, 11 Aug 2017 16:26:25 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 12:19:08 -0300
perf tools: Dedu
The initial user of this system call number is arm64.
Signed-off-by: AKASHI Takahiro
Cc: Arnd Bergmann
---
include/uapi/asm-generic/unistd.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/uapi/asm-generic/unistd.h
b/include/uapi/asm-generic/unistd.h
index 061185
This is a basic purgtory, or a kind of glue code between the two kernel,
for arm64. We will later add a feature of verifying a digest check against
loaded memory segments.
arch_kexec_apply_relocations_add() is responsible for re-linking any
relative symbols in purgatory. Please note that the purga
From: rui_feng
Signed-off-by: Rui Feng
---
drivers/mfd/rts5249.c| 154 +
drivers/mfd/rtsx_pcr.c | 177 +--
drivers/mfd/rtsx_pcr.h | 12 +++
include/linux/mfd/rtsx_pci.h | 85 +
Commit-ID: 41d3d6db1767326dd7daf7c6df48e42020647c15
Gitweb: http://git.kernel.org/tip/41d3d6db1767326dd7daf7c6df48e42020647c15
Author: Andi Kleen
AuthorDate: Fri, 10 Mar 2017 12:51:38 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 Aug 2017 12:25:11 -0300
perf vendor even
Hi all,
Changes since 20170823:
The arm64 tree gained a conflict against Linus' tree.
The net-next tree still had its build failure for which I reverted
a commit.
The wireless-drivers-next tree gained conflicts against Linus' tree.
The block tree gained a build failure so I used the version fr
Most of sha256 code is based on crypto/sha256-glue.c, particularly using
non-neon version.
Please note that we won't be able to re-use lib/mem*.S for purgatory
because unaligned memory access is not allowed in purgatory where mmu
is turned off.
Since purgatory is not linked with the other part of
load_crashdump_segments() creates and loads a memory segment of elf core
header for crash dump.
"linux,usable-memory-range" and "linux,elfcorehdr" will add to the 2nd
kernel's device-tree blob. The logic of this cod is also from kexec-tools.
Signed-off-by: AKASHI Takahiro
Cc: Catalin Marinas
Cc
1 - 100 of 944 matches
Mail list logo
