Hi Gwendal,
Overall, this looks good to me, but please make sure this is based on
upstream, and not the ChromeOS kernel trees.
On 01/30/2017 11:30 AM, Gwendal Grignou wrote:
> Add a kernel driver for GOOG0006, an ACPI driver reporting an event when
> the tablet switch status changes.
>
> On an A
On 01/25/2017 08:44 AM, Rob Rice wrote:
> Changes in v3:
> - rebase to 4.10-rc3 in cryptodev-2.6 tree
> - in bindings doc, list all valid compatibility strings
> - rename DT nodes "crypto" rather than "spu-crypto"
> - include a separate DT node for each SPU hardware block. Previously,
> there was
Hi Vinayak,
Sorry for late response. It was Lunar New Year holidays.
On Fri, Jan 27, 2017 at 01:43:23PM +0530, vinayak menon wrote:
> >
> > Thanks for the explain. However, such case can happen with THP page
> > as well as slab. In case of THP page, nr_scanned is 1 but nr_reclaimed
> > could be 51
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as
well as probe the entire driver from the I2C bus. I2C is the communication
method between the BMC and the P8 OCC.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/de
N.B. I'm not confident that this patch is ready to be included as-is.
Rather I'm hoping for guidance from reviewers and maintainers on
broad implementation choices--whether A) the bitmask of flags to invert
makes sense or B) vendor-specific is_busy() function pointers or C)
hot-patching using the a
Add a kernel driver for GOOG0006, an ACPI driver reporting an event when
the tablet switch status changes.
On an ACPI based convertible chromebook check evtest display tablet mode
switch changes:
Available devices:
..
/dev/input/event3: Tablet Mode Switch
..
Testing ... (interrupt to exit)
Ev
From: "Edward A. James"
This patchset adds a hwmon driver to support the OCC (On-Chip Controller)
on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management
Controller). The OCC is an embedded processor that provides real time
power and thermal monitoring.
The driver provides an i
From: "Edward A. James"
Add core support for polling the OCC for it's sensor data and parsing that
data into sensor-specific information.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ| 40
MAINTAINERS| 7 +
drivers/hwmon/K
On Fri, Jan 27, 2017 at 01:43:36PM +0530, Vinayak Menon wrote:
> It is noticed that during a global reclaim the memory
> reclaimed via shrinking the slabs can sometimes result
> in reclaimed pages being greater than the scanned pages
> in shrink_node. When this is passed to vmpressure, the
> unsign
On Fri, Jan 27, 2017 at 01:43:37PM +0530, Vinayak Menon wrote:
> At the end of a window period, if the reclaimed pages
> is greater than scanned, an unsigned underflow can
> result in a huge pressure value and thus a critical event.
> Reclaimed pages is found to go higher than scanned because
> of
2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글:
> Dear Thierry,
>
> Could you please review this patch?
Thierry, I think this patch has been reviewed enough but no comment from you.
Seems you are busy. I will pick up this.
Thanks.
>
> Best Regards,
> Hoegeun Kwon
>
> On 01/11/2017 03:33 PM, Ho
On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote:
> +static void imxcsi2_enable(struct imxcsi2_dev *csi2, bool enable)
> +{
> + if (enable) {
> + imxcsi2_write(csi2, 0x, CSI2_PHY_SHUTDOWNZ);
> + imxcsi2_write(csi2, 0x, CSI2_DPHY_RSTZ);
> +
From: David Gibson
To make includes more useful, dtc for some time has allowed "overlays" in
dts files, defining the tree in several chunks which are merged together.
Recent Linux kernels make use of dynamic DT overlays which have similar
mechanics, but are implemented at DT load time with specia
This series revives the new style of overlay syntax that never got
merged. David said he wanted to handle it outside of the parse
phase[1], and he proposed a patch to move overlay application to the
livetree phase. I've applied that patch and reworked Pantelis' last
two patches for the new style "s
From: Pantelis Antoniou
Add a single test making sure the &foo { }; syntax works.
Signed-off-by: Pantelis Antoniou
[stephen.b...@linaro.org: Update test to add required root node]
Signed-off-by: Stephen Boyd
---
tests/overlay_overlay_simple.dts | 3 +++
tests/run_tests.sh | 6 ++
There's typically a standard pinout for expansion boards on
platforms like raspberry pi, 96boards, C.H.I.P, etc. Introduce a
new syntax to describe these types of expansion boards in
devicetree.
In general, the resulting dtb format is very similar to the
/plugin/ style of overlays, except the 'tar
Instead of writing overlays with the target property and
__overlay__ node, i.e.
fragment@0 {
target = <&foo>;
__overlay__ {
bar-property = <0x200>;
};
}
support the syntactic sugar version of overlays where th
On Tue, Jan 24, 2017 at 03:05:21PM +0800, zhichang.yuan wrote:
> Low-pin-count interface is integrated into some SoCs. The accesses to those
> peripherals under LPC make use of I/O ports rather than the memory mapped I/O.
>
> To drive these devices, this patch introduces a method named indirect-IO
On Tue, Jan 24, 2017 at 03:05:22PM +0800, zhichang.yuan wrote:
> After indirect-IO is introduced, system must can assigned indirect-IO devices
> with logical I/O ranges which are different from those for PCI I/O devices.
> Otherwise, I/O accessors can't identify whether the I/O port is for memory
>
Many Motorola phones like droid 4 are using a custom PMIC called CPCAP
or 6556002. This PMIC is used with several SoCs, I've noticed at least
omap3, omap4 and Tegra2 based Motorola phones and tablets using it.
Cc: devicet...@vger.kernel.org
Cc: Marcel Partap
Cc: Michael Scott
Signed-off-by: Tony
On Mon, 16 Jan 2017, Christophe Leroy wrote:
> Since 2005, powerpc GCC doesn't manage anymore __stack_chk_guard as
> a global variable but as some value located at -0x7008(r2)
Is this still an "RFC" or is there a chance that this will land in 4.10?
Thanks,
Christian.
> In the Linux kernel, r2 is
From: "Edward A. James"
Add a generic mechanism to expose the sensors provided by the OCC in
sysfs.
Signed-off-by: Edward A. James
Signed-off-by: Andrew Jeffery
---
Documentation/hwmon/occ | 62 +++
drivers/hwmon/occ/Makefile| 2 +-
drivers/hwmon/occ/occ_sysfs.c | 251 +++
Hi Miklos,
Today's linux-next merge of the vfs-miklos tree got a conflict in:
fs/read_write.c
between commit:
97e147358bea ("vfs: wrap write f_ops with file_{start,end}_write()")
from the overlayfs tree and various duplicated patches between v4.10-rc1
and the vfs-miklos tree.
Please clean
On Tue, Jan 24, 2017 at 03:05:22PM +0800, zhichang.yuan wrote:
> After indirect-IO is introduced, system must can assigned indirect-IO devices
> with logical I/O ranges which are different from those for PCI I/O devices.
> Otherwise, I/O accessors can't identify whether the I/O port is for memory
>
Hi Philipp,
On 1/30/2017 3:42 AM, Philipp Zabel wrote:
> As of commit bb475230b8e5 ("reset: make optional functions really
Where can I find this? It's not in mainline.
John
> optional"), the reset framework API calls use NULL pointers to describe
> optional, non-present reset controls.
>
> Thi
On Mon, Jan 30, 2017 at 07:48:44PM +0100, Fabian Frederick wrote:
> instead of atomic_add_unless(value, -1, 0)
>
> Signed-off-by: Fabian Frederick
> ---
> fs/xfs/xfs_buf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index ac3b4d
On Wed, 2017-01-18 at 10:48 +0100, Hannes Reinecke wrote:
> @@ -1488,26 +1487,13 @@ static unsigned long disk_events_poll_jiffies(struct
> gendisk *disk)
> void disk_block_events(struct gendisk *disk)
> {
> struct disk_events *ev = disk->ev;
> - unsigned long flags;
> - bool
CONFIG_DEBUG_NX_TEST has been broken since CONFIG_DEBUG_SET_MODULE_RONX
was added in v2.6.37 via commit 84e1c6bb38eb ("x86: Add RO/NX
protection for loadable kernel modules") since the exception table was
then made read-only. Additionally, the manually constructed extables
were never fixed when rel
On 1/30/2017 4:28 PM, John Youn wrote:
> Hi Philipp,
>
> On 1/30/2017 3:42 AM, Philipp Zabel wrote:
>> As of commit bb475230b8e5 ("reset: make optional functions really
>
> Where can I find this? It's not in mainline.
>
Never mind. I found on arm-soc per your reply elsewhere.
Acked-by: John Youn
The Q6V5 in MSM8916 doesn't have a mss supply, so remove this and update
the code to support cases without proxy or active supplies.
Cc: Avaneesh Kumar Dwivedi
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/qcom_q6v5_pil.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
On Fri, Jan 06, 2017 at 06:11:18PM -0800, Steve Longerbeam wrote:
> Philipp Zabel (3):
> ARM: dts: imx6qdl: Add mipi_ipu1/2 multiplexers, mipi_csi, and their
> connections
> add mux and video interface bridge entity functions
> platform: add video-multiplexer subdevice driver
>
> Steve L
On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote:
> +++ b/drivers/staging/media/imx/imx-mipi-csi2.c
...
> +#define DEVICE_NAME "imx6-mipi-csi2"
Why is the device/driver named imx6-mipi-csi2, but the module named
imx-mipi-csi2 - could there be some consistency here please?
Thanks.
Hi Viresh,
On 2017년 01월 30일 13:50, Viresh Kumar wrote:
> On Wed, Dec 28, 2016 at 5:37 PM, Chanwoo Choi wrote:
>> +++ b/drivers/devfreq/devfreq.c
>> @@ -620,6 +620,23 @@ struct devfreq *devfreq_add_device(struct device *dev,
>> goto err_init;
>> }
>>
>> + /*
>> +
> On Mon, Jan 30, 2017 at 01:51:56PM +0300, Dan Carpenter wrote:
> > The lstcon_ioctl_entry() function doesn't have enough size checking.
>
> Actually, the lstcon_ioctl_entry() would have been fine before we apply
> this [patch 60/60]... As near as I can tell, no in kernel code is
> negatively a
It's necessary to reference the xo clock and cx supply, so specify these
in the node. Also move the Hexagon smd-edge into the hexagon node, to
enable SSR.
As cxo is not yet available we reference the fixed version of cxo for
now, which will work until proper power management is implemented.
Signe
Pushing the SCM calls into the MDT loader reduces duplication in the
callers and allows for non-remoteproc clients to use the helper for
parsing and loading MDT files.
Cc: Andy Gross
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/qcom_adsp_pil.c | 29 +---
drivers/remoteproc/qcom_
Rather than duplicating half of the MDT loader in the validation step
move the entire MDT parser into the q6v5 driver. This allows us to make
the shared MDT-loader call the SCM PAS operations directly which
simplifies the client code and allows for better reuse of the code.
Cc: Avaneesh Kumar Dwiv
With the remoteproc parts cleaned out of the MDT loader we can move it
to drivers/soc/qcom.
Cc: Andy Gross
Cc: Georgi Djakov
Cc: Jordan Crouse
Signed-off-by: Bjorn Andersson
---
For testing purposes a temporary branch containing these patches can be found
here:
https://github.com/andersson/k
In preparation for moving the mdt loader out of remoteproc let's move
the somewhat unrelated resource table dummy helper to a Qualcomm
"common" file.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/Kconfig | 6 +
drivers/remoteproc/Makefile | 1 +
drivers/remotepro
The "fw" firmware object is passed from the remoteproc core and should
not be overwritten, as that results in leaked buffers and a double free
of the the last firmware object.
Fixes: 051fb70fd4ea ("remoteproc: qcom: Driver for the self-authenticating
Hexagon v5")
Cc: sta...@vger.kernel.org
Signed
When converting a driver to managed resources it is desirable to be able to
manage all resources in the same fashion. This change allows managing clock
prepared and enabled state in the same way we manage many other resources.
This adds the following managed APIs:
- devm_clk_prepare()/devm_clk_un
Remoteproc treats the error codes returned from the stubbed SMD API as
errors, but the fact that SMD is not enabled should not affect
remoteproc's ability to start the remote processors.
Signed-off-by: Bjorn Andersson
---
include/linux/rpmsg/qcom_smd.h | 6 ++
1 file changed, 2 insertions(+)
Em Mon, Jan 30, 2017 at 01:16:18PM -0800, Joe Stringer escreveu:
> On 30 January 2017 at 12:28, Arnaldo Carvalho de Melo wrote:
> > ---
> > Thus, a return value of size or more means that the output was
> > truncated.
> > ---
> Good spotting, I looked over the committed versions and tested them,
> Wat?
>
> I'm sorry but this patch makes no sense at all.
>
> On Sat, Jan 28, 2017 at 07:04:41PM -0500, James Simmons wrote:
> > From: Bruno Faccini
> >
> > When a LBUG has occurred, without panic_on_lbug being set,
> > health_check sysfs file must return an unhealthy state.
>
> Why?
Its a
On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote:
> On Mon, Jan 30, 2017 at 10:55:51AM -0800, Stephen Boyd wrote:
> > On 01/29, Dmitry Torokhov wrote:
> > > When converting a driver to managed resources it is desirable to be able
> > > to
> > > manage all resources in the same fashion
On 01/30/2017 10:49 PM, Dave Hansen wrote:
> On 01/29/2017 07:35 PM, Anshuman Khandual wrote:
>> HugeTLB allocation/release/accounting currently spans across all the nodes
>> under N_MEMORY node mask. Coherent memory nodes should not be part of these
>> allocations. So use system_ram() call to fetc
Signed-off-by: Bjorn Andersson
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index eb5a6fc8d6f9..c8f743ef3cc8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10514,6 +10514,7 @@ S: Maintained
F: drivers/rpmsg/
F: Documentation/rpmsg.tx
-by: Randy Dunlap
Cc: Hans de Goede
---
drivers/platform/x86/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
I don't see why the "depends on INPUT" was there at all,
but I modified its requirement anyway. Maybe it can be removed...
--- linux-next-20170130.orig/dri
a92def1becf3 ("[media] ir-rx51: port to rc-core")
I have used the v4l-dvb tree from next-20170130 for today.
--
Cheers,
Stephen Rothwell
On Mon, Jan 30, 2017 at 04:41:48PM +0100, Boris Brezillon wrote:
> Rename devm_get_gpiod_from_child() into
> devm_fwnode_get_gpiod_from_child() to reflect the fact that this
> function is operating on a fwnode object.
I believe this is completely pointless rename. Are you planning on
adding devm_o
On Tue, Jan 31, 2017 at 12:45:11AM +, Russell King - ARM Linux wrote:
> Trying this driver with an imx219 camera (which works with Philipp's
> driver) results in not much happening... no /dev/media* node for it,
> no subdevs, no nothing. No clues as to what's missing either. Only
> messages f
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in:
arch/mips/configs/lemote2f_defconfig
between commit:
b3f6046186ef ("MIPS: Update lemote2f_defconfig for CPU_FREQ_STAT change")
from the mips tree and commit:
e7f73a76e07a ("cpufreq: Remove CONFIG_CPU_FREQ_STAT_DETAILS
On 01/30/2017 04:45 PM, Russell King - ARM Linux wrote:
Hi,
Trying this driver with an imx219 camera (which works with Philipp's
driver) results in not much happening... no /dev/media* node for it,
no subdevs, no nothing. No clues as to what's missing either. Only
messages from imx-media ar
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
between commit:
3e621b19b0bb ("net/mlx5e: Support TC encapsulation offloads with upper
devices")
from the net tree and commits:
75c33da82736 ("net/mlx5e: TC ipv4 tun
On Mon, Jan 30, 2017 at 04:12:53PM -0800, Christian Kujau wrote:
> On Mon, 16 Jan 2017, Christophe Leroy wrote:
> > Since 2005, powerpc GCC doesn't manage anymore __stack_chk_guard as
> > a global variable but as some value located at -0x7008(r2)
>
> Is this still an "RFC" or is there a chance tha
Move the SMD edge handling to the Qualcomm common file to make it
reusable for other Qualcomm remoteproc drivers.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/qcom_common.c | 50
drivers/remoteproc/qcom_common.h | 15 ++--
drivers/remotep
Call the common SMD edge handler to instantiate subdevices to bring
associated SMD edges up and down as the remoteproc is started and
stopped.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/Kconfig | 2 ++
drivers/remoteproc/qcom_adsp_pil.c | 6 ++
drivers/remoteproc/qcom_q6v5
In preparation for moving the mdt loader out of remoteproc let's move
the somewhat unrelated resource table dummy helper to a Qualcomm
"common" file.
Signed-off-by: Bjorn Andersson
---
drivers/remoteproc/Kconfig | 6 +
drivers/remoteproc/Makefile | 1 +
drivers/remotepro
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/cadence/macb.h
between commit:
dc97a89e726c ("net: macb: Fix 64 bit addressing support for GEM")
from the net tree and commit:
c2594d804d5c ("macb: Common code to enable ptp support for MACB/GE
On Mon, 30 Jan 2017, Ondrej Zary wrote:
>
> Also tested two CD-ROM drives and they didn't work (machine hangs). They
> didn't work before and looks like they never worked with PDMA.
>
> The fundamental problem of PDMA is that it either transfers all required
> data or it breaks horribly. Even
On Mon 30 Jan 07:03 PST 2017, Avaneesh Kumar Dwivedi wrote:
> Add smp2p support to communicate with slpi processor.
>
> Signed-off-by: Avaneesh Kumar Dwivedi
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
On 01/30/2017 11:04 PM, Dave Hansen wrote:
> On 01/29/2017 07:35 PM, Anshuman Khandual wrote:
>> * CDM node's zones are not part of any other node's FALLBACK zonelist
>> * CDM node's FALLBACK list contains it's own memory zones followed by
>> all system RAM zones in regular order as before
>> * C
On 01/30/2017 05:03 PM, Anshuman Khandual wrote:
> On 01/30/2017 10:49 PM, Dave Hansen wrote:
>> On 01/29/2017 07:35 PM, Anshuman Khandual wrote:
>>> HugeTLB allocation/release/accounting currently spans across all the nodes
>>> under N_MEMORY node mask. Coherent memory nodes should not be part of
On Mon, 2017-01-30 at 12:05 -0800, Eric Anholt wrote:
> Joe Perches writes:
>
> > On Fri, 2017-01-27 at 13:55 -0800, Eric Anholt wrote:
> > > Generated with checkpatch.pl --fix-inplace and git add -p out of the
> > > results.
> >
> > Maybe another.
> >
> > > diff --git a/drivers/staging/media/p
On 01/30/2017 05:36 PM, Anshuman Khandual wrote:
>> Let's say we had a CDM node with 100x more RAM than the rest of the
>> system and it was just as fast as the rest of the RAM. Would we still
>> want it isolated like this? Or would we want a different policy?
>
> But then the other argument bei
pmc_reprogram_counter() always sets a sample period based on the value of
pmc->counter. However, hsw_hw_config() rejects sample periods less than
2^31 - 1. So for example, a KVM guest doing
perf stat -e r2005101c4 sleep 0
will count some conditional branch events, deschedule the task, reschedule
From: Hiraku Toyooka
To test multiple pmsg, we should check that /dev/pmsg[N] (N > 0) is
available. After reboot, we should check that pmsg-[backend]-[N] which
keeps content is detected even if pmsg-[backend]-[N-M] (0 < M <= N)
doesn't exist due to lack of contents.
So this adds the following te
From: Hiraku Toyooka
This enables pmsg to deal with multiple instances. One possible
use is content priority control on limited persistent store space. By
using different buffers, we can prevent important messages from being
overwritten by less important messages.
When pstore backend module spec
This commit adds generic function __ramoops_init_prz() to reduce redundancy
between ramoops_init_prz() and ramoops_init_przs().
Signed-off-by: Nobuhiro Iwamatsu
Signed-off-by: Hiraku Toyooka
Cc: Anton Vorontsov
Cc: Colin Cross
Cc: Kees Cook
Cc: Mark Salyzyn
Cc: Seiji Aguchi
Cc: Shuah Khan
This enables ramoops to deal with multiple pmsg instances.
A User can configure the size of each buffers by its module parameter
as follows.
pmsg_size=0x1000,0x2000,...
Then, the ramoops allocates multiple buffers and tells the number
of buffers to pstore to create multiple /dev/pmsg[ID].
Sign
The following series implements multiple pmsg. This feature allows userspace
program to control individual content aging or priority.
If a pstore backend module(e.g. ramoops) requires the multiple pmsg instances
when registering itself to pstore, multiple /dev/pmsg[ID] are created. Writes
to each
On Mon, Jan 30, 2017 at 07:41:59PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers use-after-free in timerfd_remove_cancel:
> https://gist.githubusercontent.com/dvyukov/202576d437c84ffbbe52e9ccd77e1b44/raw/5562bff8626a73627157331ea2b837f59080ac84/gistfile1.txt
>
> BUG: KAS
On 01/30/2017 05:06 PM, Russell King - ARM Linux wrote:
On Tue, Jan 31, 2017 at 12:45:11AM +, Russell King - ARM Linux wrote:
Trying this driver with an imx219 camera (which works with Philipp's
driver) results in not much happening... no /dev/media* node for it,
no subdevs, no nothing. N
On 01/30/2017 04:31 PM, Russell King - ARM Linux wrote:
On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote:
+++ b/drivers/staging/media/imx/imx-mipi-csi2.c
...
+#define DEVICE_NAME "imx6-mipi-csi2"
Why is the device/driver named imx6-mipi-csi2, but the module named
imx-mipi-cs
> It looks like what happened is there were two patches applied out of
> sync. Let's add a fixes tag and CC the original author.
So the only problem here is the commit message. I will update it then.
> Fixes: ed2f549dc0f6 ("staging: lustre: libcfs: test if userland data is to
> small")
>
> T
On 01/30/2017 09:38 PM, Jiri Olsa wrote:
On Mon, Jan 30, 2017 at 07:32:03PM +0900, Taeung Song wrote:
SNIP
looks almost the same as for_each_event_system macro,
what's the difference other than 'ftrace' check?
Little thing.
In parse-events.c for_each_event macro contains
tp_event_has_id()
On Sun, Jan 29, 2017 at 2:00 PM, Ritesh Raj Sarraf wrote:
> On Sun, 2017-01-29 at 03:33 -0800, probonopd wrote:
>> Yes, I am not happy about that.
>> You could either push your change to the squashfs folks
>> Sent a PR half a year ago but no reaction: plougher/squashfs-tools#13 - is
>> something w
Hi,
On Wed, Jan 25, 2017 at 02:23:38PM -0600, Rob Herring wrote:
> Here's V3 of the serdev bus support with all the review feedback so far
> incorporated. Greg applied the first 4 patches already. I also found a
> problem in the tty_port_wakeup changes and have fixed that.
>
> I've added serdev s
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Gruszka
Cc: Wanpeng Li
Signed-off-by: Frederic Weisbecker
---
This is one more step toward converting cputime accounting to pure nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Also convert itimers to use nsec based internal counters. This simplifies
it and remove the whole game with error/inc_error which served to deal
with cputime_t random granularity.
Cc: Benjami
Now that the whole cputime conversion to nsec units is complete, we
can remove the compatibility accessors.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Tho
This is one more step toward converting cputime accounting to pure nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
cputime_t is now only used by two archs:
* powerpc (when CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y)
* s390
And since the core doesn't use it anymore, we don't need any arch support
from the others. So we can remove their stub implementations.
A final cleanup would be to provide an effi
This way we don't need to deal with cputime_t details from the core code.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
Since the core doesn't deal with cputime_t anymore, most of these APIs
have been left unused. Lets remove these.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc
This nsec based cputime_t implementation isn't used anymore. We can
remove it.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
It's unused now.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Gruszka
Cc: Wanpeng Li
Signed-off-by: Freder
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Also convert posix-cpu-timers to use nsec based internal counters to
simplify it.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidef
cputime_t is being obsolete and replaced by nsecs units in order to make
internal timestamps less opaque and more granular.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik v
It's a leftover from removed code.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Gruszka
Cc: Wanpeng Li
Sig
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
Not sure if MISDN stats are ABI but it displays task cputime in cputime_t
raw value regardless of what type cputime_t wraps which could be either
jiffies, nsecs, usecs, or whatever random time unit. Plus it wrongly
assumes that cputime_t is long.
Given that this dump is broken anyway, lets just di
Now that most cputime readers use the transition API which return the
task cputime in old style cputime_t, we can safely store the cputime in
nsecs. This will eventually make cputime statistics less opaque and more
granular. Back and forth convertions between cputime_t and nsecs in order
to deal wi
Initially, nsec based cputime_t implementation belonged to ia64. It got
exported later for CONFIG_VIRT_CPU_ACCOUNTING_GEN but now it is again
only used by ia64. So let's move it back there.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwide
This cputime_t implementation is now unused, we can remove it.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
This is one more step toward converting cputime accounting to pure nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
NSEC_PER_JIFFY is an ad-hoc redefinition of TICK_NSEC. Let's rather
use a unique and well maintained version.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: T
Kernel cpu stats are stored in cputime_t which is an architecture
defined type, and hence a bit opaque and requiring accessors and mutators
for any operation.
Converting them to nsecs simplifies the code and is one step toward
the removal of cputime_t in the core code.
Cc: Benjamin Herrenschmidt
301 - 400 of 1053 matches
Mail list logo
