On Thu, May 26, 2016 at 11:08:14AM -0700, Shaohua Li wrote:
> -int blkdev_issue_discard(struct block_device *bdev, sector_t sector,
> - sector_t nr_sects, gfp_t gfp_mask, unsigned long flags)
> +static int do_blkdev_issue_discard(struct block_device *bdev, sector_t
> sector,
We've spl
From: Nick Alcock
Date: Fri, 27 May 2016 14:19:27 +0100
> The only difference between the two series above is that in the crashing
> series, the ka_restorer stub functions __rt_sigreturn_stub and
> __sigreturn_stub (on sparc32) and __rt_sigreturn_stub (on sparc64) get
> stack-protected; in the no
Thank you or the prompt report which saved me the greater embarrassment
of seeing the bug in -rc1.
The original name was simply hash_string(), but that conflicted with a
function with that name in drivers/base/power/trace.c, and I decided that
calling it "hashlen_" was better anyway.
But you have to do it in two places.
Signed-off-by: George Spelvin
Fixes: fcfd2fbf22d2587196890103d41e3d554c47
> Reverting 468a9428521e, 2a18da7a9c78, and fcfd2fbf22d2 fixed the problem
> for me in a couple of test builds, but I don't know if all three patches
> need to be reverted, or if reverting those patches fixes the problem for
> all builds, or if the revert is sufficient.
Oh, fuck me so fucking hard
I see:
fs/dcache.c:1673: undefined reference to `hashlen_string'
For:
total: 148 pass: 22 fail: 126
I didn't bisect, but I strongly suspect commit fcfd2fbf22d2 ("fs/namei.c:
Add hashlen_string() function") because the new function is not provided
if DCACHE_WORD_ACCESS is not enabled. Th
On Fri, May 27, 2016 at 6:39 PM, Brian Norris wrote:
> Use the new ChromeOS EC EC_CMD_PWM_{GET,SET}_DUTY commands to control
> one or more PWMs attached to the Embedded Controller. Because the EC
> allows us to modify the duty cycle (as a percentage, where U16_MAX is
> 100%) but not the period, we
Instead of using device tree, assuming you have firmware control,
another way could be to add a firmware feature:
for instance, there is one EC_FEATURE_PWM_FAN, the fan PWM, one for
the keyboard lightning as well. (see num ec_feature_code)
By adding one more, you let cros_ec_dev load the platform d
From: David Miller
Date: Fri, 27 May 2016 15:51:37 -0700 (PDT)
> I'm trying to figure out the same thing myself.
Ok, mystery solved.
The basic problem is that we don't handle unaligned stacks on return to
userspace
%100 properly. We would also no handle a stack whose access would trigger a bu
---
drivers/input/input-mt.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/input/input-mt.c b/drivers/input/input-mt.c
index 54fce56..b89aaa7 100644
--- a/drivers/input/input-mt.c
+++ b/drivers/input/input-mt.c
@@ -218,8 +218,17 @@ void input_mt_report_poi
Hello,
On (05/27/16 18:04), Minchan Kim wrote:
> > It is fundamentally impossible to get a list of all *potential*
> > algorithms if you allow loadable modules. By definition someone
> > could load a new module and thus introduce a new algorithm.
>
> Thanks for the quick response. I understand n
Hi,
I am Kristi and i saw your contact through google page of your country which
impress me and i feel we can be friends to share ideals and reason together for
good,if not bad then let us know more about each other and i hope there will be
no problem for us to be friend with no bad intention.Yo
Added Vishay Capella CM36672 Proximity Sensor IIO driver. Support both
ACPI and Device Tree.
Signed-off-by: Kevin Tsai
---
.../devicetree/bindings/i2c/trivial-devices.txt| 1 +
.../devicetree/bindings/iio/light/cm36672.txt | 54 ++
MAINTAINERS
On Thu, May 26, 2016 at 9:16 AM, Viresh Kumar wrote:
> On 25-05-16, 19:53, Steve Muckle wrote:
>> The slow-path frequency transition path is relatively expensive as it
>> requires waking up a thread to do work. Should support be added for
>> remote CPU cpufreq updates that is also expensive since
The EFI firmware on Macs contains a full-fledged network stack for
downloading OS X images from osrecovery.apple.com. Unfortunately
on Macs introduced 2011 and 2012, EFI brings up the Broadcom 4331
wireless card on every boot and leaves it enabled even after
ExitBootServices has been called. The ca
The code is using the compatible DT string to associate a reset driver
with the actual device itself. The compatible string does not exist on
ACPI based systems. HID is the unique identifier for a device driver
instead.
Signed-off-by: Sinan Kaya
---
drivers/vfio/platform/vfio_platform_common.c
The device tree code checks for the presence of a reset driver and calls
the of_reset function pointer by looking up the reset driver as a module.
ACPI defines _RST method to perform device level reset. After the _RST
method is executed, the OS can resume using the device. _RST method is
expected
Open call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will abort open if reset fails.
Signed-off-by: Sinan Kaya
---
drivers/vfio/platform/vf
Getting ready to bring out extra debug information to the caller
so that more verbose information can be printed when an error is
observed.
Signed-off-by: Sinan Kaya
---
drivers/vfio/platform/vfio_platform_common.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/driv
The reset call sequence seems to replicate itself multiple times
across the file. Grouping them together for maintenance reasons.
Signed-off-by: Sinan Kaya
Reviewed-by: Eric Auger
---
drivers/vfio/platform/vfio_platform_common.c | 30 +---
1 file changed, 14 insertions(+
Release call is ignoring the return code from reset call and can
potentially continue even though reset call failed.
If reset_required module parameter is set, this patch is going
to validate the return code and will cause stack dump with
WARN_ON and warn the user of failure.
Signed-off-by: Sinan
Creating a new function to determine if this driver supports reset
function or not. This is an attempt to abstract device tree calls
from the rest of the code.
Signed-off-by: Sinan Kaya
Reviewed-by: Eric Auger
---
drivers/vfio/platform/vfio_platform_common.c | 7 ++-
1 file changed, 6 inser
The code was allowing platform devices to be used without a supporting
VFIO reset driver. The hardware can be left in some inconsistent state
after a guest machine abort.
The reset driver will put the hardware back to safe state and disable
interrupts before returning the control back to the host
of_irq_get() returns 0 iff irq_create_of_mapping() call fails. Returning
both error code and 0 on failure is a sign of a misdesigned API. Return
-ENXIO instead like one of the callers, platform_get_irq(), does; fix up
the kernel-doc as well...
Signed-off-by: Sergei Shtylyov
---
The patch is aga
On 05/28/2016 01:24 AM, Robert Jarzmik wrote:
Guenter Roeck writes:
Hi,
your mainline commit f806dac5938b ("ARM: pxa: activate pinctrl for device-tree
machines") causes various non-devicetree systems to fail with the following
error messages when running a pxa_defconfig image.
Ah yes, you're
On 05/27/2016 08:36 PM, Mark Brown wrote:
Personally the way I parse this situation is that the kernel is taking
a look at what's in the DT and making an effort to present it usefully
in the running systems. Fixing our current interpretation in stone as
a supported thing when we don't have to m
Oh! I based in on 0fed3ac866eabf01924457921ee3684c8e4c9005, which
I hope makes sense.
of_irq_get[_byname]() return 0 iff irq_create_of_mapping() call fails.
Returning both error code and 0 on failure is a sign of a misdesigned API.
We should rely on the platform IRQ resource in this case, not return 0,
especially as 0 can be a valid IRQ resource too...
Fixes: aff008ad813c ("plat
On Sat, May 28, 2016 at 12:57 PM, George Spelvin
wrote:
> Okay, Linus, it's still warm from the oven, but I think it's fully baked.
Hmm. Whioch commit did you use as a base for this? It's not plain 4.6,
but it's not toay's git either.
I did find a point where this applies, but it would be even b
The kernel-doc for the of_irq_get[_byname]() is clearly inadequate in
describing the return values -- of_irq_get_byname() is documented better
than of_irq_get() but it still doesn't mention that 0 is returned iff
irq_create_of_mapping() fails (it doesn't return an error code in this
case). Docume
That's all that's ever asked for, and it makes the return
type of hash_long() consistent.
It also allows (upcoming patch) an optimized implementation
of hash_64 on 32-bit machines.
I tried adding a BUILD_BUG_ON to ensure the number of bits requested
was never more than 32 (most callers use a comp
We'd like to make more use of the highly-optimized dcache hash functions
throughout the kernel, rather than have every subsystem create its own,
and a function that hashes basic null-terminated strings is required
for that.
(The name is to emphasize that it returns both hash and length.)
It's act
Finally, the first use of previous two patches: eliminate the
separate ad-hoc string hash functions in the sunrpc code.
Now hash_str() is a wrapper around hash_string(), and hash_mem() is
likewise a wrapper around full_name_hash().
Note that sunrpc code *does* call hash_mem() with a zero length,
This is just the infrastructure; there are no users yet.
This is modelled on CONFIG_ARCH_RANDOM; a CONFIG_ symbol declares
the existence of .
That file may define its own versions of various functions, and define
HAVE_* symbols (no CONFIG_ prefix!) to suppress the generic ones.
Included is a sel
Patch 0fed3ac866 improved the hash mixing, but the function is slower
than necessary; there's a 7-instruction dependency chain (10 on x86)
each loop iteration.
Word-at-a-time access is a very tight loop (which is good, because
link_path_walk() is one of the hottest code paths in the entire kernel)
Microblaze is an FPGA soft core that can be configured various ways.
If it is configured without a multiplier, the standard __hash_32()
will require a call to __mulsi3, which is a slow software loop.
Instead, use a shift-and-add sequence for the constant multiply.
GCC knows how to do this, but it
... so they can be used without the rest of
The hashlen_* macros will make sense next patch.
Signed-off-by: George Spelvin
---
include/linux/dcache.h | 27 +
include/linux/stringhash.h | 72 ++
2 files changed, 73 insertions(+), 2
This will improve the performance of hash_32() and hash_64(), but due
to complete lack of multi-bit shift instructions on H8, performance will
still be bad in surrounding code.
Designing H8-specific hash algorithms to work around that is a separate
project. (But if the maintainers would like to g
This provides a multiply by constant GOLDEN_RATIO_32 = 0x61C88647
for the original mc68000, which lacks a 32x32-bit multiply instruction.
Yes, the amount of optimization effort put in is excessive. :-)
Shift-add chain found by Yevgen Voronenko's Hcub algorithm at
http://spiral.ece.cmu.edu/mcm/gen
Okay, Linus, it's still warm from the oven, but I think it's fully baked.
Special thanks to J. Bruce Fields for testing and finding bugs in v1.
(I learned some humbling lessons about "obviously correct" code.)
On the arch-specific front, the m68k assembly has been tested in
a standalone test harn
The "simplified" prime multipliers made very bad hash functions, so get rid
of them. This completes the work of 689de1d6ca.
To avoid the inefficiency which was the motivation for the "simplified"
multipliers, hash_64() on 32-bit systems is changed to use a different
algorithm. It makes two calls
On Fri, May 27, 2016 at 3:08 PM, William Breathitt Gray
wrote:
> Several modern devices, such as PC/104 cards, are expected to run on
> modern systems via an ISA bus interface. Since ISA is a legacy interface
> for most modern architectures, ISA support should remain disabled in
> general. Support
Hi Krzysztof,
On 27.05.2016 14:49, Krzysztof Kozlowski wrote:
> Bring some consistency by:
> 1. Replacing fixed-space indentation of structure members with just
>tabs.
> 2. Remove indentation in declaration of local variable between type and
>name. Driver was mixing usage of such indentat
Linus,
here is the pull request from I2C with the fix for a regression
introduced yesterday. The regression didn't show up here locally because
I did not have PAGE_POISONING enabled. And buildbots discovered this
only after it hit your tree. Thanks to Dan for the quick response.
Really sorry about
Hi Kieran,
On Fri, May 27, 2016 at 7:19 PM, Kieran Bingham wrote:
> The FCP driver, can also support the FCPF variant for FDP1 compatible
> processing.
>
> Signed-off-by: Kieran Bingham
Thanks for your patch!
> ---
> Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++-
> 1 file ch
Hi Kieran,
On Fri, May 27, 2016 at 7:19 PM, Kieran Bingham wrote:
> The example misses the power-domains usage, and documentation that the
> property is used by the node.
>
> Signed-off-by: Kieran Bingham
Thanks for your patch!
> ---
> Documentation/devicetree/bindings/media/renesas,fcp.txt |
On Sat 2016-05-28 12:12:06, Pavel Machek wrote:
> Hi!
>
> It looks like redshift stopped working. Even pretty crazy settings
> have no visible effect:
>
> pavel@amd:~$ redshift -O 1500 -g 6.6:6.6:6.6
> Using method `randr'.
> pavel@amd:~$ redshift -x
> Using method `randr'.
> pavel@amd:~$ uname -
Hello,
On Fri, 27 May 2016 14:58:11 -0700, Florian Fainelli wrote:
> + if (ctrl->nand_version >= 0x0702)
> + bits = 7;
> if (ctrl->nand_version >= 0x0600)
Don't you want an "else if" here ?
Otherwise, even for the 7.2 version of your controller bits will be set
to 1.
Ditt
On Sun, May 1, 2016 at 6:38 PM, Jonathan Cameron wrote:
> On 29/04/16 12:48, Ksenija Stanojevic wrote:
>> Add mxs-lradc adc driver.
>>
>> Signed-off-by: Ksenija Stanojevic
> Mostly looking good. A few nitpicks and suggestions inline.
>
> Jonathan
>> ---
>> drivers/iio/adc/Kconfig | 37
On Sat, Apr 30, 2016 at 1:36 AM, Dmitry Torokhov
wrote:
> Hi Ksenija,
>
> On Fri, Apr 29, 2016 at 01:49:11PM +0200, Ksenija Stanojevic wrote:
>> Add mxs-lradc touchscreen driver.
>>
>> Signed-off-by: Ksenija Stanojevic
>> ---
>> drivers/input/touchscreen/Kconfig| 14 +-
>> drivers/input
On Sun, May 1, 2016 at 6:47 PM, Jonathan Cameron wrote:
> On 29/04/16 12:49, Ksenija Stanojevic wrote:
>> Add mxs-lradc touchscreen driver.
>>
>> Signed-off-by: Ksenija Stanojevic
> The only real thing this raises for me is why we are grabbing IRQs that I
> don't think this driver even cares abou
On 27/05/16 23:09, William Breathitt Gray wrote:
> With the introduction of the ISA_BUS_API Kconfig option, ISA-style
> drivers may be built for X86_64 architectures. This patch changes the
> ISA Kconfig option dependency of the Apex Embedded Systems STX104 DAC
> driver to ISA_BUS_API, thus allowin
Replace if condition and BUG() with a BUG_ON having the conditional
expression of the if statement as argument.
The Coccinelle semantic patch used to make this change is as follows:
@@ expression E,f; @@
(
if (<+... f(...) ...+>) { BUG(); }
|
- if (E) { BUG(); }
+ BUG_ON(E);
)
Signed-off-by: A
Replace if condition and BUG() with a BUG_ON having the conditional
expression of the if statement as argument.
The Coccinelle semantic patch used to make this change is as follows:
@@ expression E,f; @@
(
if (<+... f(...) ...+>) { BUG(); }
|
- if (E) { BUG(); }
+ BUG_ON(E);
)
Signed-off-by: A
> These kinds of use after frees don't always cause a runtime problem. I
> found it using static analysis, but I bet you could detect it if you
> enabled kasan. The other option is to enable PAGE_POISONING?
Thanks, PAGE_POISONING did trigger the issue. So, I now picked up your
patch instead of
Hi Linus,
The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:
Linux 4.6-rc4 (2016-04-17 19:13:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform.git
tags/chrome-platform
for you to fetch changes up
On second thought, I went with the revert instead. Generating pull request now.
-Olof
On Fri, May 27, 2016 at 7:37 PM, Olof Johansson wrote:
> On Thu, May 26, 2016 at 4:07 AM, Enric Balletbo i Serra
> wrote:
>> Hi Benson, Olof
>>
>> On 26/05/16 03:59, Benson Leung wrote:
>>> This reverts commi
Hi Boris,
I have the same feeling as Mychaela, and suffered from the 'high-level
controllers' as well.
Looking forward to your review, thanks!
Best regards,
Keguang Zhang
On 05/28/2016 08:12 PM, Boris Brezillon wrote:
> Hi Kelvin,
>
> On Sat, 28 May 2016 17:54:10 +0800
> Keguang Zhang wrote:
>
From: Masami Hiramatsu
To improbe usability, support %[PROVIDER:]SDTEVENT format to
add new probes on SDT and cached events.
e.g.
# perf probe -x /lib/libc-2.17.so %lll_lock_wait_private
Added new event:
sdt_libc:lll_lock_wait_private (on %lll_lock_wait_private in
/usr/lib/libc
From: Masami Hiramatsu
perf probe --list shows all cached probes when --cache
is given. Each caches are shown with on which binary that
probed. e.g.
-
# perf probe --cache vfs_read \$params
# perf probe --cache -x /lib64/libc-2.17.so getaddrinfo \$params
# perf probe --cache --list
Support @BUILDID or @FILE suffix for SDT events. This allows
perf to add probes on SDTs/pre-cached events on given FILE
or the file which has given BUILDID (also, this complements
BUILDID.)
For example, both gcc and libstdc++ has same SDTs as below.
If you would like to add a probe on sdt_libstdcxx
From: Hemant Kumar
This patch serves the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section ".note.stapsdt". To
find
these markers from the bina
From: Masami Hiramatsu
Skip SDTs placed in invalid (non-exist, or older version)
binaries. Note that perf-probe --cache --list and
perf-probe --cache --del still handle all the caches
including invalid binaries.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in v7
From: Masami Hiramatsu
perf buildid-cache --add scans given binary and add
the SDT events to probe cache. "sdt_" prefix is appended for
all SDT providers to avoid event-name clash with other pre-defined
events. It is possible to use the cached SDT events as other cached
events, via perf probe --
From: Masami Hiramatsu
perf-probe --del removes caches when --cache is given.
Note that the delete pattern is not same as normal events.
If you cached probes with event name, --del "eventname"
works as expected. However, if you skipped it, the cached
probes doesn't have actual event name. In tha
Support a special SDT probe format which can omit the '%' prefix
only if the SDT group name starts with "sdt_". So, for example
both of "%sdt_libc:setjump" and "sdt_libc:setjump" are acceptable
for perf probe --add.
Suggested-by: Brendan Gregg
Signed-off-by: Masami Hiramatsu
---
tools/perf/Docu
Allo glob wildcard for reusing cached/SDT events. This also
automatically find the target binaries, e.g.
# perf probe -a %sdt_libc:\*
This example adds probes for all SDT in libc.
Note that the SDTs must have been scanned by perf buildid-cache.
Signed-off-by: Masami Hiramatsu
---
Changes in
From: Masami Hiramatsu
Show SDT and pre-cached events by perf-list with "sdt". This also
shows the binary and build-id where the events are placed only
when there are same name events on different binaries.
e.g.
# perf list sdt
List of pre-defined events (to be used in -e):
sdt_l
From: Masami Hiramatsu
Before analyzing debuginfo, try to find a corresponding entry
from probe cache always. This does not depend on --cache,
the --cache enables to store/update cache, but looking up
the cache is always enabled.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
From: Masami Hiramatsu
Allow user to set group name for adding new event.
Note that user must ensure that the group name doesn't
conflict with existing group name carefully.
E.g. Existing group name can conflict with other events.
Especially, using the group name reserved for kernel
modules can h
Introduce filename__readable to check readability by opening
the file directly. Since the access(R_OK) just checks the
readability based on real UID/GID, it is ignored that the
effective UID/GID and capabilities for some special file (e.g.
/proc/kcore).
filename__readable() directly opens given fil
From: Masami Hiramatsu
Use path/to/bin/buildid/elf instead of path/to/bin/buildid
to store corresponding elf binary.
This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms.
Note that the existing caches are not updated until user adds
or updates the cache. Anyway, if there is the ol
Hi,
Here is the 9th version of the patchset for probe-cache and
initial SDT support.
The previous version is here; https://lkml.org/lkml/2016/5/14/107
This version just fixes 2 points according to Hemant's comment,
and split out the filename__readable() patch.
Changes in v9:
- [1/16,2/16] sp
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in v6:
- Remove unneeded O_APPEND from open(). (Thanks Namhyung!)
- Fix to
Cleanup the code flow of dso__find_kallsyms() to remove
redundant checking code and add some comment for readability.
Signed-off-by: Masami Hiramatsu
---
Changes in v9:
- Split into filename__readable() and others.
Changes in v8:
- Add comments why we can't use access(R_OK) for /proc/kcore
res is initialized to 0 in befs_get_block() but this value will be
overwritten before it is used.
Signed-off-by: Luis de Bethencourt
---
Hi,
Saw this small issue while reading the code. BeFS is very interesting, and
reading this code is very educational after reading Dominic Giampaolo's book.
W
Hi Andy,
On Fri, May 27, 2016 at 4:00 AM, Andy Lutomirski wrote:
> Currently, the trace_printk code chooses which static buffer to use based
> on what type of atomic context (NMI, IRQ, etc) it's in. Simplify the
> code and make it more robust: simply count the nesting depth and choose
> a buffer
Hi,
On 16-05-16 19:06, Chen-Yu Tsai wrote:
Hi,
On Sun, May 15, 2016 at 1:55 AM, Hans de Goede wrote:
The axp20x pmics have 2 power inputs, one called ACIN which is intended
for to be supplied via a powerbarrel on the board and one called VBUS
which is intended to be supplied via an otg connec
Original Message
From: Baoquan HE
If not valid just skip reserving the old domain id.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu.c | 4
drivers/iommu/amd_iommu_init.c | 5 +++--
drivers/iommu/amd_iommu_types.h | 5 +
3 files changed, 8 insertion
Original Message
From: Baoquan HE
Here several things need be done:
1) Initialize amd_iommu_dev_table because it was set several times
since kdump kernel reboot. We don't need the set because we will
copy the content from old kernel.
2) Re-enable event/cmd buffer
3) In
On Thursday, May 26, 2016 10:29:45 AM Viresh Kumar wrote:
> On 26-05-16, 00:23, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The modularity of cpufreq_stats is quite problematic.
> >
> > First off, the usage of policy notifiers for the initialization
> > and cleanup in the cpufre
On Fri, May 27, 2016 at 4:38 PM, Logan Gunthorpe wrote:
> If you tried to write two spads in one line, as per the example:
>
> root@peer# echo '0 0x01010101 1 0x7f7f7f7f' > $DBG_DIR/peer_spad
>
> then the CPU would freeze in an infinite loop.
>
> This wasn't immediately obvious but 'pos' was not i
alloc_bootmem function never returns NULL. Thus a NULL test after a
call to this function is unnecessary.
The Coccinelle semantic patch used to make this change is follows:
@@
expression E;
statement S;
@@
E =
alloc_bootmem(...)
... when != E
- if (E == NULL) S
Signed-off-by: Amitoj Kaur Chawla
Original Message
Add function copy_dev_tables to copy old DTE of the 1st kernel to
the new DTE table. Since all iommu share the same DTE table the
copy only need be done once as long as the physical address of
old DTE table is retrieved from iommu reg. Besides the old domain
i
Replace if condition and BUG() with a BUG_ON having the conditional
expression of the if statement as argument.
The Coccinelle semantic patch used to make this change is as follows:
@ disable unlikely @ expression E,f; @@
(
if (<+... f(...) ...+>) { BUG(); }
|
- if (unlikely(E)) { BUG(); }
+ BU
Original Message
Add functions to check whether translation is already enabled in IOMMU.
Signed-off-by: Baoquan He
---
drivers/iommu/amd_iommu_init.c | 25 +
drivers/iommu/amd_iommu_types.h | 4
2 files changed, 29 insertions(+)
diff --git a/
There is a generic function __pvclock_read_cycles to be used to get both
flags and cycles. For function pvclock_read_flags, it's useless to get
cycles value. To make this function be more effective, get this variable
flags directly in function.
Signed-off-by: Minfei Huang
---
v1:
- Get rid of __p
On 2016/5/28 19:59, He Kuang wrote:
This patch extracts codes related to specific arithecture out of
unwind-libunwind.c. The extrated part are only built if local
libunwind is supported.
Signed-off-by: He Kuang
---
tools/perf/util/Build| 1 +
tools/perf/util/unwind-li
Hi Kelvin,
On Sat, 28 May 2016 17:54:10 +0800
Keguang Zhang wrote:
> From: Kelvin Cheung
>
> This patch adds NAND driver for Loongson1B.
I think your controller matches Mychaela's "high-level NAND controller"
definition [1]. Mychaela, can you confirm the Loongson controller
looks like yours?
Currently, perf script uses host unwind methods to parse perf.data
callchain info regardless of the target architecture. So we get wrong
result without any warnings when unwinding callchains of x86(32-bit)
on x86(64-bit) machine.
This patch shows warning messages when we do remote unwind x86(32-bi
Currently, libunwind operations are fixed, and they are chosen
according to the host architecture. This will lead a problem that if a
thread is run as x86_32 on x86_64 machine, perf will use libunwind
methods for x86_64 to parse the callchain and get wrong result.
This patch changes the fixed meth
On 05/27/16 at 06:06P, Paolo Bonzini wrote:
>
>
> On 27/05/2016 17:40, Andy Lutomirski wrote:
> > On Thu, May 26, 2016 at 11:17 PM, Minfei Huang wrote:
> >> There is a generic function __pvclock_read_cycles to be used to get both
> >> flags and cycles. For function pvclock_read_flags, it's usele
CONFIG_LIBUNWIND/NO_LIBUNWIND are changed to
CONFIG_LOCAL_LIBUNWIND/NO_LOCAL_LIBUNWIND for retaining local unwind
features.
The new CONFIG_LIBUNWIND stands for either local or remote or both
unwind are supported.
Signed-off-by: He Kuang
---
tools/perf/arch/arm/util/Build | 2 +-
tools/perf/a
v5 url:
http://thread.gmane.org/gmane.linux.kernel/2226821
Currently, perf script uses host unwind methods(local unwind) to parse
perf.data callchain info regardless of the target architecture. So we
get wrong result and no promotion when do remote unwind on other
platforms/machines.
This patch
For determine the libunwind methods to use, we should get the
32bit/64bit information from maps of a thread. When a thread is newly
created, the information is not prepared. This patch moves
unwind__prepare_access() into thread__insert_map() so we can get the
information we need from maps.
Signed-
Currently, the type of thread->addr_space is unw_addr_space_t, which
is a pointer defined in libunwind headers. For local libunwind, we can
simple include "libunwind.h", but for remote libunwind, the header
file is depends on the target libunwind platform. This patch uses
'void *' instead to decoup
Support x86(32-bit) cross platform callchain unwind.
Signed-off-by: He Kuang
---
tools/perf/arch/Build | 1 +
tools/perf/arch/x86/util/unwind-libunwind.c| 7 ---
tools/perf/arch/x86/util/unwind-libunwind_x86_32.c | 21 +
tools/perf/u
Pass LIBUNWIND_DIR to feature check flags for remote libunwind
tests. So perf can be able to detect remote libunwind libraries from
arbitrary directory.
Signed-off-by: He Kuang
---
tools/perf/config/Makefile | 9 +
1 file changed, 9 insertions(+)
diff --git a/tools/perf/config/Makefile
For local libunwind, it uses the fixed methods to convert register id
according to the host platform, but in remote libunwind, this convert
function should be the one for remote architechture. This patch
changes the fixed name to macro and code for each remote platform can
be compiled indivadually.
Export normalize_arch() function, so other part of perf can get
normalized form of arch string.
Signed-off-by: He Kuang
---
tools/perf/arch/common.c | 2 +-
tools/perf/arch/common.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/perf/arch/common.c b/tools/perf/arch/co
1 - 100 of 165 matches
Mail list logo
