TCE tables might get too big in case of 4K IOMMU pages and DDW enabled
on huge guests (hundreds of GB of RAM) so the kernel might be unable to
allocate contiguous chunk of physical memory to store the TCE table.
To address this, POWER8 CPU (actually, IODA2) supports multi-level TCE tables,
up to 5
Normally a bitmap from the iommu_table is used to track what TCE entry
is in use. Since we are going to use iommu_table without its locks and
do xchg() instead, it becomes essential not to put bits which are not
implied in the direction flag.
This adds iommu_direction_to_tce_perm() (its counterpar
On Monday 09 March 2015 11:56:22 Geert Uytterhoeven wrote:
> On Mon, Mar 9, 2015 at 11:50 AM, Geert Uytterhoeven
> wrote:
> > JFYI, when comparing v4.0-rc3[1] to v4.0-rc2[3], the summaries are:
> > - build errors: +18/-7
>
> + /home/kisskb/slave/src/arch/arm/mach-pxa/idp.c: error:
> 'SMC91X_N
Before the IOMMU user would take control over the IOMMU table belonging to
a specific IOMMU group. This approach did not allow sharing tables between
IOMMU groups attached to the same container.
This introduces a new IOMMU ownership flavour when the user can not
just control the existing IOMMU tab
The pnv_pci_ioda_tce_invalidate() helper invalidates TCE cache. It is
supposed to be called on IODA1/2 and not called on p5ioc2. It receives
start and end host addresses of TCE table. This approach makes it possible
to get pnv_pci_ioda_tce_invalidate() unintentionally called on p5ioc2.
Another issu
Hi,
On Mon, Mar 09, 2015 at 12:26:21PM +, Tc, Jenny wrote:
> > > + char name[PSY_MAX_BAT_NAME_LEN];
> >
> > char *name;
> >
> > No need for arbitrary length limitation.
>
> The length limitation is introduced to form a packed structure so that
> the data can be read directly from memory wit
This is a part of moving DMA window programming to an iommu_ops
callback.
This is a mechanical patch.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/platforms/powernv/pci-ioda.c | 85 ---
1 file changed, 56 insertions(+), 29 deletions(-)
diff --git a/arch/powe
This changes few functions to receive a iommu_table_group pointer
rather than PE as they are going to be a part of upcoming
iommu_table_group_ops callback set.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/platforms/powernv/pci-ioda.c | 13 -
1 file changed, 8 insertions(+), 5
This enables sPAPR defined feature called Dynamic DMA windows (DDW).
Each Partitionable Endpoint (IOMMU group) has an address range on a PCI bus
where devices are allowed to do DMA. These ranges are called DMA windows.
By default, there is a single DMA window, 1 or 2GB big, mapped at zero
on a PC
I just stumbled over this in -RT. The code:
87 bool irq_work_queue(struct irq_work *work)
88 {
…
96 /* If the work is "lazy", handle it from next tick if any */
97 if (work->flags & IRQ_WORK_LAZY) {
98 if (llist_add(&work->llnode, this_cpu_ptr(&lazy_list)) &&
The iommu_free_table helper release memory it is using (the TCE table and
@it_map) and release the iommu_table struct as well. We might not want
the very last step as we store iommu_table in parent structures.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/include/asm/iommu.h | 1 +
arch/
At the moment only one group per container is supported.
POWER8 CPUs have more flexible design and allows naving 2 TCE tables per
IOMMU group so we can relax this limitation and support multiple groups
per container.
This adds TCE table descriptors to a container and uses iommu_table_group_ops
to
This clears the TCE table when a container is being closed as this is
a good thing to leave the table clean before passing the ownership
back to the host kernel.
Signed-off-by: Alexey Kardashevskiy
---
drivers/vfio/vfio_iommu_spapr_tce.c | 14 +++---
1 file changed, 11 insertions(+), 3 d
This checks that the TCE table page size is not bigger that the size of
a page we just pinned and going to put its physical address to the table.
Otherwise the hardware gets unwanted access to physical memory between
the end of the actual page and the end of the aligned up TCE page.
Since compoun
On Monday, March 09, 2015 08:55:46 AM Alexandre Belloni wrote:
> Hi,
>
> On 08/03/2015 at 02:12:53 +0100, Rafael J. Wysocki wrote :
> > > > I think you misunderstood, that is exactly the expected behaviour. This
> > > > is hardware defined. Once the watchdog is started, nobody can stop it.
> > > >
This patch removes "Enable USB3 LPM Capability" option from Kconfig
and adds snps,usb3_lpm_capable devicetree property instead of it.
USB3 LPM (Link Power Management) capability is hardware property, and
it's platform dependent, so if our hardware supports this feature, we
want rather to configure
On 03/09/2015 02:55 PM, Marc Kleine-Budde wrote:
> On 03/09/2015 02:53 PM, Jean Delvare wrote:
>> Le Monday 09 March 2015 à 10:56 +0100, Marc Kleine-Budde a écrit :
>>> On 03/09/2015 10:52 AM, Michal Simek wrote:
On 03/09/2015 10:13 AM, Marc Kleine-Budde wrote:
> On 03/09/2015 09:58 AM, Mi
Old code was trying to avoid having three branch insns,
but instead it has a chain of six insns where each insn
depends on previos one.
And it was touching PT_OLDSS(%esp) unconditionally, even when it may
contain bogus data. Elsewhere we have to jump thru hoops
just to make sure here PT_OLDSS(%esp
On Mon, Mar 09, 2015 at 07:23:43PM +0530, Sudip Mukherjee wrote:
> On Mon, Mar 09, 2015 at 04:38:05PM +0300, Dan Carpenter wrote:
> >
> >
> > On Mon, Mar 09, 2015 at 07:00:33PM +0530, Sudip Mukherjee wrote:
> > > On Mon, Mar 09, 2015 at 04:13:43PM +0300, Dan Carpenter wrote:
> > > > On Sun, Mar 0
> hum, so people using CSV mode will now see extra 2 numbers
> at the end of the line:
>
> $ ./perf.old stat -x, -e cycles ls > /dev/null
> 2679161,,cycles
> $ ./perf stat -x, -e cycles ls > /dev/null
> 2574169,,cycles,1295544,100.00
>
> we could be breaking existing scripts..
I doubt it
Enable the xilinx driver for ARM64.
Signed-off-by: Michal Simek
Acked-by: Sören Brinkmann
---
Changes in v2:
- Based on discussion with Marc and Jean enable this driver just for
ARM64.
BTW: Jean suggested to enable it for all ARM platforms but it is
just not needed that's why I am just addin
Test basic openat(2) behaviour.
Test that if O_BENEATH flag is set, openat() will only
open paths that have no .. component and do not start
with /. Symlinks are also checked for the same restrictions.
Signed-off-by: David Drysdale
---
.gitignore| 1 +
common/openat | 61
Signed-off-by: David Drysdale
---
man2/open.2 | 32
1 file changed, 32 insertions(+)
diff --git a/man2/open.2 b/man2/open.2
index 956531b24b26..be40dd7710df 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -716,6 +716,31 @@ XFS support was added
.\" commit ab297431
Add a new O_BENEATH flag for openat(2) which restricts the
provided path, rejecting (with -EPERM) paths that are not beneath
the provided dfd. In particular, reject:
- paths that contain .. components
- paths that begin with /
- symlinks that have paths as above.
Also disallow use of nd_jump_l
On 2015/3/6 20:50, Joe Perches wrote:
On Fri, 2015-03-06 at 17:33 +0800, Chentao (Boby) wrote:
#ifdef pr_fmt
#undef pr_fmt
#endif
#define pr_fmt(fmt) "xen-pvscsi: " fmt
No, just use add
#define pr_fmt(fmt) "xen-pvscsi: " fmt
before the first #include.
The #ifdef/#undef/#endif isn't necessary
On Mon, Mar 9, 2015 at 6:44 AM, Denys Vlasenko wrote:
> On Mon, Mar 9, 2015 at 2:35 PM, Andy Lutomirski wrote:
>>> Apparently, code which uses this still exists, here
>>> (current git):
>>>
>>> restore_all:
>>> TRACE_IRQS_IRET
>>> restore_all_notrace:
>>> #ifdef CONFIG_X86_ESPFIX32
>>>
This change adds a new O_BENEATH flag for openat(2) which restricts the
provided path, rejecting (with -EPERM) paths that are not beneath
the provided dfd.
This change was originally included as part of a larger patchset
(https://lkml.org/lkml/2014/7/25/426) for Capsicum support; however, it
is po
Acked-by: Chad Dupuis
On Wed, 4 Mar 2015, Nicholas Mc Guire wrote:
return type of wait_for_completion_timeout is unsigned long not int. An
appropriately named variable of type unsigned long is added and the
assignments fixed up.
Signed-off-by: Nicholas Mc Guire
---
The was only compile test
Looks ok.
Acked-by: Chad Dupuis
On Wed, 4 Mar 2015, Nicholas Mc Guire wrote:
return type of wait_for_completion_timeout is unsigned long not int. rc
is appropriately renamed, changed to type unsigned long and the
assignments fixed up.
Signed-off-by: Nicholas Mc Guire
---
The was only compi
The cfi_staa_write_buffers function uses a large amount of ernel stack
whenever CONFIG_MTD_MAP_BANK_WIDTH_32 is set, and that results in a
warning on ARM allmodconfig builds:
drivers/mtd/chips/cfi_cmdset_0020.c: In function 'cfi_staa_write_buffers':
drivers/mtd/chips/cfi_cmdset_0020.c:651:1: warni
On Tue, Mar 3, 2015 at 9:47 AM, Alexey Brodkin
wrote:
> It's possible that boot-loader that worked on CPU before Linux kernel
> made some changes in GPIO controller registers. For example interrupts
> could be all masked.
>
> Current implementation of DW GPIO driver relies on default values in
>
On 2015/3/6 20:53, Juergen Gross wrote:
On 03/06/2015 09:34 PM, Tao Chen wrote:
Add the {xen-pvscsi: } prefix in pr_fmt and remove DPRINTK, then
replace all DPRINTK with pr_debug.
Also fixed up some comments just as eliminate redundant whitespace
and format the code.
These will make the code
On 03/09/2015 02:53 PM, Jean Delvare wrote:
> Le Monday 09 March 2015 à 10:56 +0100, Marc Kleine-Budde a écrit :
>> On 03/09/2015 10:52 AM, Michal Simek wrote:
>>> On 03/09/2015 10:13 AM, Marc Kleine-Budde wrote:
On 03/09/2015 09:58 AM, Michal Simek wrote:
> On 03/09/2015 09:50 AM, Marc Kl
Le Monday 09 March 2015 à 10:56 +0100, Marc Kleine-Budde a écrit :
> On 03/09/2015 10:52 AM, Michal Simek wrote:
> > On 03/09/2015 10:13 AM, Marc Kleine-Budde wrote:
> >> On 03/09/2015 09:58 AM, Michal Simek wrote:
> >>> On 03/09/2015 09:50 AM, Marc Kleine-Budde wrote:
> On 03/09/2015 09:48 AM
On Mon, Mar 09, 2015 at 04:38:05PM +0300, Dan Carpenter wrote:
>
>
> On Mon, Mar 09, 2015 at 07:00:33PM +0530, Sudip Mukherjee wrote:
> > On Mon, Mar 09, 2015 at 04:13:43PM +0300, Dan Carpenter wrote:
> > > On Sun, Mar 08, 2015 at 11:10:11PM +0530, Sudip Mukherjee wrote:
> > > > change return typ
Hi Alex,
The subject of this change has a typo, and I also think it's not about
exposing the pause state (that's just an internal name/concept), but
about exposing the PSCI state, or simply the VCPU power state.
On Mon, Mar 02, 2015 at 01:29:00PM +, Alex Bennée wrote:
> To cleanly restore an
On Sat, Mar 7, 2015 at 6:56 PM, Adrian Remonda wrote:
> diff --git a/Documentation/spi/spidev_test.c b/Documentation/spi/spidev_test.c
> index 3a2f9d59edab..533050ced9f1 100644
> --- a/Documentation/spi/spidev_test.c
> +++ b/Documentation/spi/spidev_test.c
> @@ -15,6 +15,7 @@
> #include
> #incl
On Mon, Mar 9, 2015 at 8:24 AM, Matt Porter wrote:
> The imx-pwm binding contains language indicating compatible
> strings to be used that is not valid for all supported parts
> e.g. Should be "fsl,-pwm". Fix this by enumerating the
> valid compatible strings that represent the two versions of
> t
This patch adds runtime pm handling to dw_mmc.
It mainly uses mci_request/mci_request_end for mmc host state information.
The goal of the runtime pm in dw_mmc host is mainly for giving an information
for containing it power domain about its activity.
Signed-off-by: Karol Wrona
Acked-by: Kyungmin
On Sunday, March 08, 2015 11:43:34 AM Alan Stern wrote:
> On Sat, 7 Mar 2015, Rafael J. Wysocki wrote:
>
> > But this is part of a bigger picture. Namely, if a separete wakeup
> > interrupt
> > is required for a device, the device's power.can_wakeup flag cannot be set
> > until that interrupt ha
Hello,
This patch adds runtime pm for dw_mmc. There is no runtime pm callbacks for
exynos dw_mmc because the host hardware gates interface clock itself and it is
done separately. The reason for runtime is mainly get an info about host state
for now.
>From v1:
- move all pm_runtime funct
* Mike Galbraith | 2015-02-18 12:21:54 [+0100]:
>On Mon, 2015-02-16 at 12:18 +0100, Sebastian Andrzej Siewior wrote:
>
>> Known issues:
>>
>> - lazy preempt on x86_64 leads to a crash with some load.
>
>The below still works for me. (it doesn't make nohz_full actually work
>in rt, but at le
On 03/09/2015 01:37 PM, Sakari Ailus wrote:
Hi Jacek,
On Mon, Mar 09, 2015 at 01:19:32PM +0100, Jacek Anaszewski wrote:
Hi Sakari,
Thanks for the review.
On 03/09/2015 11:54 AM, Sakari Ailus wrote:
Hi Jacek,
On Wed, Mar 04, 2015 at 05:14:31PM +0100, Jacek Anaszewski wrote:
This patch adds
Alter 'taks' -> 'task'
Signed-off-by: Yaowei Bai
---
mm/oom_kill.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 642f38c..5d6a458 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -408,7 +408,7 @@ bool oom_killer_disabled __read_mostly;
On Mon, Mar 9, 2015 at 6:28 AM, Denys Vlasenko wrote:
> Before the patch, tss.stack field was not referenced anywhere.
> It was used only by setting sysenter's stack to point after
> last byte of tss, thus the trailing field, stack[64], was used.
> But grep would not know it. You can comment it ou
On Mon, Mar 9, 2015 at 2:35 PM, Andy Lutomirski wrote:
>> Apparently, code which uses this still exists, here
>> (current git):
>>
>> restore_all:
>> TRACE_IRQS_IRET
>> restore_all_notrace:
>> #ifdef CONFIG_X86_ESPFIX32
>> movl PT_EFLAGS(%esp), %eax # mix EFLAGS, SS and CS
>>
On 03/05/2015 08:31 AM, Antoine Tenart wrote:
> Use the nand framework helpers: onfi_get_async_timing_mode() and
> onfi_async_timing_mode_to_sdr_timings() to retrieve the timing
> configuration. Then update the pxa3xx timing setup function to use the
> timing configuration retrieved.
>
> Signed-of
On Mon, Mar 09, 2015 at 07:00:33PM +0530, Sudip Mukherjee wrote:
> On Mon, Mar 09, 2015 at 04:13:43PM +0300, Dan Carpenter wrote:
> > On Sun, Mar 08, 2015 at 11:10:11PM +0530, Sudip Mukherjee wrote:
> > > change return type of sm7xx_vga_setup() to void as we are not using
> > > the return type an
On Mon, Mar 9, 2015 at 5:55 AM, Denys Vlasenko wrote:
> On Sun, Mar 8, 2015 at 8:41 PM, Andy Lutomirski wrote:
>>> It seems to be true that 32-bit x86 always has two unused words
>>> beyond "struct pt_regs" on stack during syscalls.
>>>
>>> IOW: tss.sp0 is *not* set at the very end of the stack o
On Mon, Mar 09, 2015 at 07:30:07AM +0100, Willy Tarreau wrote:
> On Sun, Mar 08, 2015 at 11:07:25PM +0530, Sudip Mukherjee wrote:
> >
> > - if (parport_register_driver(&panel_driver)) {
> > - pr_err("could not register with parport. Aborting.\n");
> > - return -EIO;
> > -
> Maybe the next release of the board we will upgrade the serial block to the
> new version.
> but the issue is that how we circumvent this problem in kernel?
What is the official vendor workaround ?
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Mon, Mar 09, 2015 at 04:13:43PM +0300, Dan Carpenter wrote:
> On Sun, Mar 08, 2015 at 11:10:11PM +0530, Sudip Mukherjee wrote:
> > change return type of sm7xx_vga_setup() to void as we are not using
> > the return type anywhere. if this function fails we fall back to the
> > default configuratio
Please pull these fixes for the TPM driver.
---
The following changes since commit 9eccca0843205f87c00404b663188b88eb248051:
Linux 4.0-rc3 (2015-03-08 16:09:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
for-linus
Before the patch, tss.stack field was not referenced anywhere.
It was used only by setting sysenter's stack to point after
last byte of tss, thus the trailing field, stack[64], was used.
But grep would not know it. You can comment it out, compile,
and kernel will even run until an unlucky NMI corru
On Mon, Mar 09, 2015 at 06:25:03PM +0530, Sudip Mukherjee wrote:
> Actually I thought, since this is a vendor crude driver there will be many
> such changes, so if i can combine some changes together then atleast the
> number of patches can be kept low and also i thought of clubbing these
> chan
Hello,
Now that %pb[l] formatting is now in mainline, this can go forward.
Here's the updated patch which uses printf instead of the fixed buffer
when printing cpus. I couldn't find a better option at the moment and
am still appending the output to sysrq-t. This only prints out the
workqueues an
There is a notifier that handles live patches for coming and going modules.
It takes klp_mutex lock to avoid races with coming and going patches but
it does not keep the lock all the time. Therefore the following races are
possible:
1. The notifier is called sometime in STATE_MODULE_COMING. The
Em Mon, Mar 09, 2015 at 12:09:58PM +0100, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo wrote:
>
> > [...]
> >
> > Further investigation is needed to figure out the nature of the
> > objdump output change so as to make the parser grok it.
>
> Btw., maybe someone finds this interesting:
2015-03-09 19:44 GMT+08:00 Kishon Vijay Abraham I :
> Hi,
>
>
> On Thursday 05 March 2015 07:27 AM, Axel Lin wrote:
>>
>> The defines in phy-miphy365x.h are all covered in phy.h:
>>
>> MIPHY_TYPE_SATA == PHY_TYPE_STA
>> MIPHY_TYPE_PCIE == PHY_TYPE_PCIE
>> MIPPHY_TYPE_USB == PHY_TYPE_USB2
>>
>> So c
The imx-pwm binding contains language indicating compatible
strings to be used that is not valid for all supported parts
e.g. Should be "fsl,-pwm". Fix this by enumerating the
valid compatible strings that represent the two versions of
this peripheral in use.
The binding is also missing the clocks
On 03/09/2015 12:29 PM, Mike Galbraith wrote:
> On Mon, 2015-03-09 at 12:07 +0100, Sebastian Andrzej Siewior wrote:
>> On 03/09/2015 11:51 AM, Mike Galbraith wrote:
>>> Why do both mutex and rtmutex then exist one might ask? ;-) No big deal
>>> either way though, it's not like it becomes immutable
Em Sat, Mar 07, 2015 at 02:45:24PM +0200, Adrian Hunter escreveu:
> On 4/03/2015 3:07 a.m., Arnaldo Carvalho de Melo wrote:
> >Em Wed, Mar 04, 2015 at 10:01:23AM +0900, Namhyung Kim escreveu:
> >>On Tue, Mar 03, 2015 at 01:49:40PM -0300, Arnaldo Carvalho de Melo wrote:
> >>> Just a preview, but t
This patch contains the generated header file of the following
change "drm/msm/mdp5: Get SMP client list from mdp5_cfg".
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5.xml.h | 41 ++---
1 file changed, 7 insertions(+), 34 deletions(-)
diff --git a
From: Daniel Mack
This patch adds the policy database implementation.
A policy database restricts the possibilities of connections to own,
see and talk to well-known names. It can be associated with a bus
(through a policy holder connection) or a custom endpoint.
By default, buses have an empty
Hi,
On 02/24/2015 04:21 PM, Peter Ujfalusi wrote:
> Hi,
>
> The series adds support for DMA router type of devices. They are used in SoCs
> which has more peripherals with DMA request lines than the DMA controller can
> handle.
> The router itself is not part of the DMA controller and it's operat
On Mon, Mar 9, 2015 at 6:04 AM, Denys Vlasenko wrote:
> On Sat, Mar 7, 2015 at 9:37 AM, tip-bot for Andy Lutomirski
> wrote:
>> Commit-ID: a7fcf28d431ef70afaa91496e64e16dc51dccec4
>> Gitweb:
>> http://git.kernel.org/tip/a7fcf28d431ef70afaa91496e64e16dc51dccec4
>> Author: Andy Lutomirski
From: Daniel Mack
A connection chooses which metadata it wants to have attached to each
message it receives with kdbus_cmd_hello.attach_flags. The metadata
will be attached as items to the messages. All metadata refers to
information about the sending task at sending time, unless otherwise
stated
This change contains the generated header file for the following
change "drm/msm/mdp5: Separate MDP5 domain from MDSS domain".
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5.xml.h | 203 +++-
1 file changed, 118 insertions(+), 85 deletions(-)
diff
On Mar 9, 2015 7:46 AM, "Ingo Molnar" wrote:
>
>
> * Andy Lutomirski wrote:
>
> > >> */
> > >> unsigned longstack[64];
> > >>
> > >> Last I checked, 0x100 != 64. Also, wow, this is kind of disgusting. :)
> > >
> > >
> > > Seems to be unused: I commented it out on "defconfig" bui
From: Daniel Mack
Provide a walk-through example that explains how to use the low-level
ioctl API that kdbus offers. This example is meant to be useful for
developers who want to gain a in-depth understanding of how the kdbus
API works by reading a well-documented real-world example.
This progra
This patch set contains a couple modifications of the MDP5 register
description, followed by the MDP hw configuration of the msm8016 and
msm8916 chipsets.
Stephane Viau (5):
drm/msm/mdp5: Update headers (introduce MDP5 domain)
drm/msm/mdp5: Separate MDP5 domain from MDSS domain
drm/msm/mdp5:
SMP blocks are configured for specific client IDs (ports).
These client IDs can be different from one chip to another for a
given pipe.
e.g.: DMA0 pipe fetch Y component is connected to:
- port #10 for MDP5 v1.3
- port #4 for MDP5 v1.6
In order to be compatible for upcoming versions of MDP5, th
On Sun, Mar 08, 2015 at 11:10:11PM +0530, Sudip Mukherjee wrote:
> change return type of sm7xx_vga_setup() to void as we are not using
> the return type anywhere. if this function fails we fall back to the
> default configuration.
>
> Signed-off-by: Sudip Mukherjee
Reviewed-by: Dan Carpenter
T
From: Daniel Mack
This patch adds the name registry implementation.
Each bus instantiates a name registry to resolve well-known names
into unique connection IDs for message delivery. The registry will
be queried when a message is sent with kdbus_msg.dst_id set to
KDBUS_DST_ID_NAME, or when a reg
This change adds the hw configuration for msm8x16 chipsets in
mdp5_cfg module.
Note that only one external display interface is present in this
configuration (DSI) but has not been enabled yet. It will be enabled
once drm/msm driver supports DSI connectors.
Signed-off-by: Stephane Viau
---
driv
MDP block is actually contained inside the MDSS block. For some
chipsets, the base address of the MDP registers is different from the
current (assumed) 0x100 offset.
Like CTL and LM blocks, this changes introduce a dynamic offset
for the MDP instance, which can be found out at runtime, once the
M
SMP blocks are configured for specific client IDs (ports).
These client IDs can be different from one chip to another for a
given pipe.
e.g.: DMA0 pipe fetch Y component is connected to:
- port #10 for MDP5 v1.3
- port #4 for MDP5 v1.6
In order to be compatible for upcoming versions of MDP5, th
On Sun, Mar 8, 2015 at 10:43 PM, Pandruvada, Srinivas
wrote:
> On Fri, 2015-03-06 at 08:51 -0500, Josh Boyer wrote:
>> On Thu, Mar 5, 2015 at 8:37 PM, Zhang, Rui wrote:
>> > Please attach the acpidump output.
>>
>> Attached for my machine.
>>
> There is no INT3401 in the acpi dump. Also no one re
From: Daniel Mack
Add the logic to handle the following entities:
Domain:
A domain is an unamed object containing a number of buses. A
domain is automatically created when an instance of kdbusfs
is mounted, and destroyed when it is unmounted.
Every domain offers its own 'control' device
MDP block is actually contained inside the MDSS block. For some
chipsets, the base address of the MDP registers is different from the
current (assumed) 0x100 offset.
Like CTL and LM blocks, this changes introduce a dynamic offset
for the MDP instance, which can be found out at runtime, once the
MD
From: Daniel Mack
Add the basic driver structure.
handle.c is the main ioctl command dispatcher that calls into other parts
of the driver.
main.c contains the code that creates the initial domain at startup, and
util.c has utility functions such as item iterators that are shared with
other file
From: Daniel Mack
This patch adds code for matches and notifications.
Notifications are broadcast messages generated by the kernel, which
notify subscribes when connections are created or destroyed, when
well-known-names have been claimed, released or changed ownership,
or when reply messages ha
kdbus is a kernel-level IPC implementation that aims for resemblance to
the the protocol layer with the existing userspace D-Bus daemon while
enabling some features that couldn't be implemented before in userspace.
The documentation in the first patch in this series explains the
protocol and the A
From: Daniel Mack
This patch hooks up the build system to actually compile the files
added by previous patches. It also adds an entry to MAINTAINERS to
direct people to Greg KH, David Herrmann, Djalal Harouni and me for
questions and patches.
Signed-off-by: Daniel Mack
Signed-off-by: David Herr
From: Daniel Mack
This patch adds the header file which describes the low-level
transport protocol used by various ioctls. The header file is located
in include/uapi/linux/ as it is shared between kernel and userspace,
and it only contains data structure definitions, enums and defines
for constan
From: Daniel Mack
kdbusfs is a filesystem that will expose a fresh kdbus domain context
each time it is mounted. Per mount point, there will be a 'control'
node, which can be used to create buses. fs.c contains the
implementation of that pseudo-fs. Exported inodes of 'file' type have
their i_fop
From: Daniel Mack
This patch adds code to create and destroy connections, to validate
incoming messages and to maintain the queue of messages that are
associated with a connection.
Note that connection and queue have a 1:1 relation, the code is only
split in two parts for cleaner separation and
On 03/09/2015 01:50 AM, Michal Simek wrote:
Remove Kconfig dependency and enable driver for
all ARCHs.
Signed-off-by: Michal Simek
---
Test for all archs done by Kbuild test robot without any problem.
Looks ok. To be sure, I'll run it through my test farm as well.
Reviewed-by: Guenter Roeck
From: Daniel Mack
A pool for data received from the kernel is installed for every
connection of the bus, and it is used to copy data from the kernel to
userspace clients, for messages and other information.
It is accessed when one of the following ioctls is issued:
* KDBUS_CMD_MSG_RECV, to re
Added Matteo to the CC list because he was working on this function as
well and I remembered something I wanted to tell him.
On Sun, Mar 08, 2015 at 07:46:37PM +0200, Giedrius Statkevičius wrote:
> Currently the label is only used to return a error code to the caller but more
> repeating code is b
On Sat, Mar 7, 2015 at 9:37 AM, tip-bot for Andy Lutomirski
wrote:
> Commit-ID: a7fcf28d431ef70afaa91496e64e16dc51dccec4
> Gitweb: http://git.kernel.org/tip/a7fcf28d431ef70afaa91496e64e16dc51dccec4
> Author: Andy Lutomirski
> AuthorDate: Fri, 6 Mar 2015 17:50:19 -0800
> Committer: Ingo
On Thu, Mar 05, 2015 at 09:40:41AM +0800, Axel Lin wrote:
> Prefer devm_kcalloc over devm_kzalloc with multiply.
>
> Signed-off-by: Axel Lin
Acked-by: Antoine Tenart
> ---
> drivers/phy/phy-berlin-sata.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/phy
On Sun, Mar 8, 2015 at 3:13 PM, Denys Vlasenko wrote:
> On Sat, Mar 7, 2015 at 1:33 AM, Andy Lutomirski wrote:
>> On Fri, Mar 6, 2015 at 3:30 PM, Fengguang Wu wrote:
>>> Greetings,
>>>
>>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>>
>>> git://git.kernel.org/pub/
etheless, you're correct that having the bugfixes (1,2,5), then the
> optimization (4), then the janitorial fix (3) is the logical order for
> history & bisection sake. So.. I'll re-order the patches, individually
> test with the new order, and re-submit over c
On Sun, Mar 8, 2015 at 8:41 PM, Andy Lutomirski wrote:
>> It seems to be true that 32-bit x86 always has two unused words
>> beyond "struct pt_regs" on stack during syscalls.
>>
>> IOW: tss.sp0 is *not* set at the very end of the stack on 32-bit.
>
> So maybe the idea is that, if we end up using s
Dear Mark,
Thanks very much for you suggestion.
On Fri, 2015-03-06 at 11:13 +, Mark Rutland wrote:
> On Fri, Mar 06, 2015 at 10:48:18AM +, yong...@mediatek.com wrote:
> > From: Yong Wu
> >
> > This patch add smi binding document.
>
> Please move binding documents to the start of t
On Mon, Mar 09, 2015 at 03:42:22PM +0300, Dan Carpenter wrote:
> On Mon, Mar 09, 2015 at 01:05:06PM +0530, Sudip Mukherjee wrote:
> > kbuild test robot reported that for microblaze-allyesconfig
> > chan_to_field() and lynxfb_ops_set_par() were not defined. These two
> > functions were defined under
On Sat, Mar 07, 2015 at 02:07:15PM -0800, Yinghai Lu wrote:
...
I ended up committing this. Anything I've missed?
---
From: Yinghai Lu
Date: Sat, 7 Mar 2015 14:07:15 -0800
Subject: [PATCH] x86/setup: Use init_size instead of run_size
Commit
e6023367d779 ("x86, kaslr: Prevent .bss from overl
Hi Linus,
Please pull fbdev fixes:
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
tags/fbdev-fixes-4.0
for you to
From: "Suzuki K. Poulose"
This is a collection of fixes which denies grouping hardware events
from different PMUs. They also fix crashes triggered by perf_fuzzer
on Linux-4.0-rc2.
Pawel,
Similar fix is required in ARM CCN PMU driver. I didn't find it
straight forward to fix it there. Could you
701 - 800 of 1074 matches
Mail list logo
