Hello!
>> BTW, you could just combine both patches. I guess you didn't to
>> maintain authorship?
>OK. Will squash both of these patches, unless Pavel do not any objections.
I don't.
Kind regards.
ssing. Is it
intentional, so that it goes later?
Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia
Hello!
> This patch should not be applied independently without the fix in
> mainline:
>
> 0de58f852875a0f0dcfb120bb8433e4e73c7803b
> (ARM/arm64: KVM: correct PTE uncachedness check, 2015-12-03)
It's ok, both are queued.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung
from what we are implementing now.
Just curious.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia
MSI window out of target's RAM. But how does this
work on a PC then? What if our host is PC, and we
want to emulate some ARM board, which has RAM at FE00 ? Or does it mean
that PC architecture is flawed and can reliably handle
PCI passthrough only for itself ?
Kind regards,
Pav
ng
In (1) we have only a single old file, shouldn't this be cleaned up and
shouldn't this file be moved to (2)?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
administrative rules always have priority. So let it just be
this way.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
is small bit:
http://www.spinics.net/lists/linux-samsung-soc/msg49008.html
?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord.
regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Saturday, December 12, 2015 11:06 PM
> To: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman; sta..
All series:
Reviewed-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-Original Message-
From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
Behalf Of Sunil Goutham
Sent: Thursday, December 10, 2015 10:55 AM
b/drivers/net/ethernet/cavium/thunder/nicvf_queues.h
> @@ -10,6 +10,7 @@
> #define NICVF_QUEUES_H
>
> #include
> +#include "nic.h"
> #include "q_struct.h"
>
> #define MAX_QUEUE_SET128
> @@ -75,7 +76,7 @@
> */
> #defin
inner_l4_offset:8;
> + u64inner_l3_offset:8;
> + u64tso_start:8;
> + u64rsvd3:2;
> u64tso_max_paysize:14; /* W1 */
> #elif defined(__LITTLE_ENDIAN_BITFIELD)
> u64tot_len:20;
> u64rsvd1:4;
> u64l3_offset:8;
> u64
Tested-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
> Behalf Of Sunil
> Goutham
> Sent: Monday, December 07, 20
errata patches (also posted on lists, all
merged into 4.4), took defconfig, adjusted it according to my needs, and this
is what i'm running on my board and this is what i'm using for development. If
you point me at what i'm doing wrong way, i'll be glad to accept this.
I'
ng in guest i tried to apply it to host. With total of
128 virtual functions (= 128 interfaces) it does not work at all. Even after
bumping cma region size to insane value of 2GB more than half of interfaces
still failed to allocate queues. And after setting cma=3G i could not mount my
rootfs.
l BGX driver patches on my 4.2 host
kernel build. It fails to send NIC_MBOX_MSG_BGX_LINK_CHANGE, so nothing works.
I have retested this series on top of 4.3 running on ThunderX. It has good BGX
driver and everything works fine. Therefore, the
whole series can be safely applied and...
Tested-by:
Just a reminder, we have issue with this one too, which is not addressed yet.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
> Behalf
from version
to version. I enabled it and rebuilt the kernel, but in order to get the driver
working with this patch i had to also add cma=32M option to kernel arguments.
With default of 16M the allocation still fails.
Should we add Kconfig dependencies?
Kind regards,
Pavel Fedin
Expert Enginee
ool?
3. The driver could check value of atomic_pool_size and adjust own memory
requirements accordingly. This indeed looks like a quick hack, but would at
least make things running quickly.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this
patch aimed
> for linux-4.5 ?
Why not? It's just a networking driver. And, i also have the same problem on
4.3 running as KVM guest with VFIO.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsub
Hello!
This one causes the network to stop working on Fedora 21. Probably has to do
with NetworkManager, which sees something unexpected.
IP address is never set up and connection is never activated, despite it has UP
flag.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics
/0x84
[] SyS_sendmsg+0x10/0x20
thunder-nicvf 0002:01:08.4 enP2p1s8f4: Failed to alloc/config VF's QSet
resources
--- cut ---
And none of interfaces work after this. Reverting this patch helps.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
arch/arm/boot/dts/exynos5410.dtsi | 6
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Also, fix size of SROMc mapping in the example.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
Acked-by: Rob Herring
---
.../bindings/arm/samsung
ixed code style, now better understood.
v2 => v3:
- Fixed up SROMc region size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in device tree
- Improved documentation
Pavel Fedin (4):
Documentation: dt-bindings: Describe SR
function
during probe, it is changed to use PMT_CTRL register.
The problem could be observed on SMDK5410 board.
Signed-off-by: Pavel Fedin
---
drivers/net/ethernet/smsc/smsc911x.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/net/ethernet/smsc
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Also, fix size of SROMc mapping in the example.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/exynos-srom.txt
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
arch/arm/boot/dts/exynos5410.dtsi | 6
size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in device tree
- Improved documentation
Pavel Fedin (4):
Documentation: dt-bindings: Describe SROMc configuration
ARM: dts: Add SROMc to Exynos 5410
drivers: exynos-srom
x27;t have anything to change, do i? Or is it
just a formal requirement to RESEND? I can do this, if you want to.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
n the compatible string. Anyway, your problem
> to deal with.
Of course, my thought is that if compatible string is different,
then it's already a different device. And of course it would have different
parameters.
So, OK, i'll post new version with fixed documentation today.
Kind r
is the way to go.
So, what do you really think?
BTW, where is Steve, whose address is specified in MAINTAINERS for this code?
Is it abandonware?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscri
phy-mode = "mii";
> > + interrupt-parent = <&gpx0>;
> > + interrupts = <5 8>;
> > + reg-io-width = <2>;
> > + smsc,irq-push-pull;
> > + smsc,
Hello! So, what should we do with this?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
> Behalf Of Pavel
> Fedin
> Sent: Monday, Novem
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
arch/arm/boot/dts/exynos5410.dtsi | 6
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Also, fix size of SROMc mapping in the example.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/exynos-srom.txt
s, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in device tree
- Improved documentation
Pavel Fedin (4):
Documentation: dt-bindings: Describe SROMc configuration
ARM: dts: Add SROMc to Exynos 5410
drivers: exynos-srom: Add support for bank configuration
ARM: dts
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
, however, varies from 1 to 32, but the value is
from 0 to 31, i. e. - 1
What shall we do? Just document this, or adjust the code to take number of
cycles and subtract 1? To tell the truth, i'm already
sick of these small fixups, and i would prefer just to fix documentation.
Kind reg
ild devices will not be probed.
- These additional properties now have "samsung,srom-XXX" format
- Fixed code style, now better understood.
v2 => v3:
- Fixed up SROMc region size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index 4603356..e2b58f8 100644
--- a/arch
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
---
arch/arm/mach-exynos/Kconfig
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
arch/arm/boot/dts/exynos5410.dtsi | 6 +
2 files changed, 47
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Also, fix size of SROMc mapping in the example.
Signed-off-by: Pavel Fedin
---
.../bindings/arm/samsung/exynos-srom.txt | 71 +-
1 file
t;
> Although this is different board, but okay.
I am curious too, so i examined SMSC datasheet. The IRQ is fully programmable
on
chip's side too, and our driver indeed defaults to active-low. You can switch it
to active-high by addint smsc,irq-active-high property. But i just copie
GPIO settings according to chip datasheet i have. They are
actually chip-specific, but i wrote them in board
file because on different boards you may use different banks, and therefore
different pins. Or, if you don't use SROMc at all, you
can configure all pins to do something else.
Kind
er will be able to spot and fix all
broken banks at once, instead of doing one-by-one.
I have renamed the variable to 'bool bad_bank_config', will this be OK?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send th
ree, i've just checked,
0003 applies with a small fuzz and 0004 applies without problems at all.
> If they don't, they will need rebasing by someone. Maybe you can take
> care of them?
Of course. Please notify me if rebasing will be needed, i'll do it.
> You have the SMDK5
nd
my patch actually doesn't need it. I could do some
blind modifications, but cannot test them, and this is out of my scope at all.
As mentioned in the commit msg, i need only 0003 and 0004 from there. Can they
be picked up independently? They don't need 0002 by
themselves, only 000
them up and
include
into my set.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.ker
This machine uses own SoC device tree file, add missing part.
We insert the complete description, with ranges, because we are going to
connect devices to it. Values in ranges are SoC-specific, so they go here
in order not to duplicate them for every machine.
Signed-off-by: Pavel Fedin
---
arch
d.
- These additional properties now have "samsung,srom-XXX" format
- Fixed code style, now better understood.
v2 => v3:
- Fixed up SROMc region size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
---
arch/arm/mach-exynos/Kconfig
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Signed-off-by: Pavel Fedin
---
.../bindings/arm/samsung/exynos-srom.txt | 68 +-
1 file changed, 66 insertions(+), 2 deletions(-)
diff
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 40 +++
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410
rst, but it didn't work, and ranges translation
> > gave me something really weird (like addr = 0x80 and
> > size = 0x0404).
>
> Did you change the address-cells to <1>?
Of course i did.
I don't quote the rest because i simply agree to what you've said
gt; convention of wrapping at 72-char.
I know, sorry, this is MS Outlook (not Express), and it's impossible
to configure it this way (if i just set up word wrap, it starts to
corrupt patches). I am now trying to wrap the text by hands, i hope
it's better. And i cannot use anything e
t; the chip should have been already set up. In order to be able to function
> > during probe, it is changed to use PMT_CTRL register.
> >
> > The problem could be observed on SMDK5410 board.
> >
> > Signed-off-by: Pavel Fedin
>
> I'm pretty sure this is g
n top of SROMc.
This is more like a bus-specific extra. It's similar to "reg" property having
different meanings for different buses.
> Probably you can check suggestions from Krzysztof, where he pointed out
> some hint on how other places this is getting used.
Did
.
my PDF has "confidential" watermark on it, and this would mean that i
essentially copy some information from it into Linux doc. Is
it okay to do this?
If you still dislike the array, i'll redo is a set of properties like
samsung,srom-tacs, samsung,srom-tcos, etc.
Kind reg
function
during probe, it is changed to use PMT_CTRL register.
The problem could be observed on SMDK5410 board.
Signed-off-by: Pavel Fedin
---
drivers/net/ethernet/smsc/smsc911x.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/net/ethernet/smsc
> I think this is not correct. We can't change binding of "smsc,lan9115"
> which is already documented here [1]. These samsung specific srom
> properties should be in srom node or its subnode, but not in this way.
So, if you look at gpmc-eth.txt, you'll see that this
g here, I am not able to find V4 1/4 and 3/4 in this mailing
> list.
Which mailing list is "this"? I've just rechecked, i've got my messages back
on both (linux-samsung-soc and linux-arm-kernel).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Rus
Hello!
> -Original Message-
> From: linux-samsung-soc-ow...@vger.kernel.org
> [mailto:linux-samsung-soc-ow...@vger.kernel.org]
> On Behalf Of Pankaj Dubey
> Sent: Thursday, October 29, 2015 8:28 PM
> To: Pavel Fedin
> Cc: devicet...@vger.kernel.org; linux-arm-ker..
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
1 file changed, 41 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Signed-off-by: Pavel Fedin
---
.../bindings/arm/samsung/exynos-srom.txt | 50 +-
1 file changed, 48 insertions(+), 2 deletions(-)
diff
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
---
arch/arm/mach-exynos/Kconfig
ave "samsung,srom-XXX" format
- Fixed code style, now better understood.
v2 => v3:
- Fixed up SROMc region size in the device tree
- Reordered patches, documentation goes first now
v1 => v2:
- Fixed some typos and bad labels in device tree
- Improved documentation
Pavel Fedin (4):
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
---
arch/arm/boot/dts/exynos5410.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index 4603356..da6a8fa0e
Hello!
> You may need to fetch again?
> Anyway the branch is v4.4-next/driver-samsung or tags/samsung-driver...
> Or just for-next should be fine I think.
Thank you very much, already found it, and even posted my series, you should
have already seen it.
Kind regards,
Pavel Fed
Hello!
> Applied, this whole series.
Where can i find the recent code to base my series on? I looked at
linux-samsung.git but was unable to find it there.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the l
5410. By the way, what is current status? If this is final
revision, can i post my Ethernet support patchset on top
of it?
Tested-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsu
Hello!
> can we add the "depends on ... && PM" now, later, once
> you'll extend it, you remove it again?
Yes, you can. However, i think i'll post my patches as soon as the code gets
integrated into some repository, before it even goes
to the RC. So, it'
rch/330862.html.
Patch 0003 has been acked-by, and nothing more since
that.
Actually, only 0002 and 0003 of this series are needed for the pin controller.
0001 has been accepted
(27284129522e7e2a5b89e80bd44ea3345f79c9e8).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Researc
hould be "proper" for
> the time being (which could mean !PM dependency). If there is a need,
> then the dependency will be removed.
I can do it later if you prefer.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from
one small problem with their code. "bank" parameter is
device-wide, therefore you
cannot configure more than one bank. For SMDK boards it's OK, but in future you
may run into problem
with this.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
ommentations?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-inf
Hello!
> From: Pavel Fedin
>
> After GICv2m was enabled for 32-bit ARM kernel, a warning popped up:
Thank you for the cooperation, i'm now back from my vacation.
What about the first patch in the series, which actually enables GICv2m on 32
bits? I don't see it anywhere
Commit-ID: 157add60cb35913b8a848a3d7e6456b8ed134796
Gitweb: http://git.kernel.org/tip/157add60cb35913b8a848a3d7e6456b8ed134796
Author: Pavel Fedin
AuthorDate: Sun, 13 Sep 2015 12:14:33 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 15 Sep 2015 17:06:29 +0200
irqchip/GICv2m: Fix
tract the proper
> information from the device tree. We are going to piggyback on that for
> the next versions of the patch.
Where can i take a look at the code?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send th
034..18e3757 100644
> --- a/include/linux/irqchip/arm-gic-v3.h
> +++ b/include/linux/irqchip/arm-gic-v3.h
> @@ -389,6 +389,8 @@ int its_cpu_init(void);
> int its_init(struct device_node *node, struct rdists *rdists,
>struct irq_domain *domain);
>
> +typedef u32 (*its_
Tested-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: Eric Auger [mailto:eric.au...@linaro.org]
> Sent: Monday, August 03, 2015 6:31 PM
> To: eric.au...@st.com; eric.au...@linaro.org;
>
c code, which
> returns -EINVAL atm. So I plan to introduce this capability already with
> the ITS emulation series, so we can just pick it up in the IRQ routing
> series.
Then may be you follow https://lkml.org/lkml/2015/7/7/115 and replace flag
with something like
KVM_SIGNAL_EXT_MSI io
Certain platforms (e. g. BSD-based ones) define some ELF constants according
to host.
This patch fixes problems with cross-building Linux kernel on these platforms
(e. g. building ARM
32-bit version on x86-64 host).
Signed-off-by: Pavel Fedin
---
If you are not fond of mentioning Cygwin in
ld throw it away
completely and invent
KVM_SIGNAL_EXT_MSI ioctl for sending MSIs with device ID. This would also be
consistent IMO.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-ker
ID_DEVID and we
already have 'flags'
field. Using them would just make the API more consistent because
KVM_SIGNAL_MSI already uses them
in absolutely the same manner. That's my point and nothing more.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Researc
> Just so I'm sure I understand: The way the kernel differentiates between
> no-devid and devid==0, is whether or not the devid flag is set, correct?
Yes, exactly.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this lis
_MSI_VALID_DEVID;
kvm_gsi_routing_allowed = true;
kvm_msi_via_irqfd_allowed = true;
}
--- cut ---
I can post my sets as RFCs to qemu mailing list, if you want to take a look at
the whole change
set.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To un
my modified qemu now has kvm_msi_flags global variable which
defaults to 0. ITS
code, then, if activated, changes it to KVM_MSI_VALID_DEVID, and qemu starts
supplying device IDs to
the related calls.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To u
Hi!
> OK so both of you say the same thing. Will respin accordingly
You may also want to add this:
Tested-by: Pavel Fedin
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
Hello!
> OK thanks for sharing. I need some more time to study qemu code too.
I am currently working on supporting this in qemu. Not ready yet, need some
time. But, with API i
suggest, things are really much-much simpler.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Resea
I think to keep using the type for homogeneity.
Homogeneity is perfect IMHO.
If that would be simpler for you, i could post a patch for this which i made
on top of your series.
Sorry, i don't have time to respin the whole thing, busy with qemu GICv3 fight
:)
Kind regards,
Pavel Fedin
Expert
else
schedule_work(&irqfd->inject);
--- cut ---
You apparently missed KVM_IRQ_ROUTING_EXTENDED_MSI here, as well as in
irqfd_update(). But, if you
accept my API proposal, this becomes irrelevant.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Rese
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-
struct kvm_irq_routing_msi msi;
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Kind regards,
Pavel
1 - 100 of 119 matches
Mail list logo
