From: Zhi Yong Wu
The patchset implements network hub stead of vlan. The main work was done by
stefan, and i only rebased it to latest QEMU upstream, did some testings and
will be responsible for pushing it to QEMU upstream.
Stefan Hajnoczi (12):
net: Add a hub net client
net: Use hubs for
From: Stefan Hajnoczi
Stop using the special-case vlan code in net.c. Instead use the hub net
client to implement the vlan feature. The next patch will remove vlan
code from net.c completely.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
net.c | 46 ++
From: Stefan Hajnoczi
The vlan feature can be implemented in terms of hubs. By introducing a
hub net client it becomes possible to remove the special case vlan code
from net.c and push the vlan feature out of generic networking code.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
-
From: Stefan Hajnoczi
The vlan feature is implemented using hubs and no longer uses
special-purpose VLANState structs that are accessible as qdev
properties.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
hw/qdev-properties.c | 72 -
From: Stefan Hajnoczi
VLANState is no longer used and can be removed.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
net.c | 127 ++---
net.h |8
net/socket.c |6 +-
net/tap.c |6 +-
net/
From: Stefan Hajnoczi
There is no longer a distinction between vlan clients and non-vlan
clients in the net core. The net core only knows about point-to-point
clients which are connected to a peer. It's time to rename the global
list of net clients since it no longer refers to vlans at all.
Si
From: Stefan Hajnoczi
The vlan implementation in net.c has been replaced by hubs so we can
remove the code.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
hw/xen_nic.c |1 -
net.c| 108 --
net.h|1
From: Stefan Hajnoczi
Checks can be performed to make sure that hubs have at least one NIC and
one host device, warning the user if this is not the case.
Configurations which do not meet this rule tend to be broken but just
emit a warning. This patch preserves compatibility with the checks
perfo
From: Stefan Hajnoczi
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
net.c | 28 +---
net/hub.c | 24
net/hub.h |2 ++
net/slirp.c |5 +++--
4 files changed, 30 insertions(+), 29 deletions(-)
diff --git a/ne
From: Stefan Hajnoczi
Now that VLANClientState has been renamed to NetClientState all 'vc'
local variables should be 'nc'. Much of the code already used 'nc' but
there are places where 'vc' needs to be renamed.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
hw/ne2000.h |
From: Stefan Hajnoczi
Since hubs are now used to implement the 'vlan' feature and the vlan
argument is always NULL, remove the argument entirely and update all net
clients that use qemu_new_net_client().
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
net.c | 27
From: Stefan Hajnoczi
Another step in moving the vlan feature out of net core. Users only
deal with NetClientState and therefore qemu_del_vlan_client() should be
named qemu_del_net_client().
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Zhi Yong Wu
---
hw/e1000.c |2 +-
hw/eepro100.
On Thu, Mar 8, 2012 at 3:27 PM, Alexandre DERUMIER wrote:
> Hi,
>
> i'm trying to build the last kvm git,
>
> ./configure --prefix=/usr --datadir=/usr/share/kvm
> --docdir=/usr/share/doc/pve-qemu-kvm --sysconfdir=/etc --disable-xen
> --enable-vnc-tls --enable-sdl --enable-uuid --enable-linux-aio
On Thu, Mar 8, 2012 at 5:48 PM, George Bottas wrote:
> I have a question regarding changing the queue size that is set in
> virtio_blk_init(). The current value is 128, which results in setting the
> queue depth in the Windows guest device to 8. Does anyone know if changing
> this value to defi
On Thu, Mar 8, 2012 at 11:56 PM, Ross Becker wrote:
> I just joined in order to chime in here-
>
> I'm seeing the exact same thing as Reeted; I've got a machine with a
> storage subsystem capable of 400k IOPs, and when I punch the storage up to
> VMs, each VM seems to top out at around 15-20k IOP
Il 09/03/2012 10:00, zwu.ker...@gmail.com ha scritto:
> +/* TODO use qemu_send_packet() or need to call *_deliver_* directly?
> */
> +/* TODO ignore return value? */
> +qemu_send_packet(&port->nc, buf, len);
Did you see my message at
http://permalink.gmane.org/gmane.comp.
The kvm kernel module includes a number of trace events which can be
useful when debugging system behavior. Even on production systems these
trace events can be used to observe guest behavior and identify the
source of problems.
The kvm_flightrecorder script is a command-line wrapper for the
/sys
On Thu, Mar 8, 2012 at 6:47 PM, Richard Earnshaw
wrote:
> On 08/03/12 17:21, Nicolas Pitre wrote:
>> On Thu, 8 Mar 2012, Richard Earnshaw wrote:
>>
>>> On 02/03/12 21:15, Nicolas Pitre wrote:
So, to me, the gcc documentation is perfectly clear on this topic.
there really _is_ a guarantee
On Fri, 9 Mar 2012, Dave Martin wrote:
> Register variables feel like a red herring though. We're only using
> those because we can't do the needful thing and actually desscribe
> these constraints in the asm constraints (which would seem to be the
> right place). We specifically don't care wher
On 09/03/12 16:20, Nicolas Pitre wrote:
> On Fri, 9 Mar 2012, Dave Martin wrote:
>
>> Register variables feel like a red herring though. We're only using
>> those because we can't do the needful thing and actually desscribe
>> these constraints in the asm constraints (which would seem to be the
>>
Jan Kiszka wrote:
> On 2012-03-06 08:49, Liu, Jinsong wrote:
>> Jan,
>>
>> Any comments? I feel some confused about your point 'disable cpuid
>> feature for older machine types by default': are you planning a
>> common approach for this common issue, or, you just ask me a
>> specific solution for
On 2012-03-09 19:27, Liu, Jinsong wrote:
> Jan Kiszka wrote:
>> On 2012-03-06 08:49, Liu, Jinsong wrote:
>>> Jan,
>>>
>>> Any comments? I feel some confused about your point 'disable cpuid
>>> feature for older machine types by default': are you planning a
>>> common approach for this common issue,
Jan Kiszka wrote:
> On 2012-03-09 19:27, Liu, Jinsong wrote:
>> Jan Kiszka wrote:
>>> On 2012-03-06 08:49, Liu, Jinsong wrote:
Jan,
Any comments? I feel some confused about your point 'disable cpuid
feature for older machine types by default': are you planning a
common app
On 03/08/2012 06:49 AM, Marcelo Tosatti wrote:
The following changes since commit e32605062cd62c2a958ad28a6ad7de4eeab12027:
xilinx_zynq: machine model initial version (2012-03-07 02:20:19 +0100)
Pulled. Thanks.
Regards,
Anthony Liguori
are available in the git repository at:
git://
Liu, Jinsong wrote:
> Jan Kiszka wrote:
>> On 2012-03-06 08:49, Liu, Jinsong wrote:
>>> Jan,
>>>
>>> Any comments? I feel some confused about your point 'disable cpuid
>>> feature for older machine types by default': are you planning a
>>> common approach for this common issue, or, you just ask me
On 03/09/2012 08:13 AM, Stefan Hajnoczi wrote:
The kvm kernel module includes a number of trace events which can be
useful when debugging system behavior. Even on production systems these
trace events can be used to observe guest behavior and identify the
source of problems.
The kvm_flightrecor
On 2012-03-09 20:09, Liu, Jinsong wrote:
> Jan Kiszka wrote:
>> On 2012-03-09 19:27, Liu, Jinsong wrote:
>>> Jan Kiszka wrote:
On 2012-03-06 08:49, Liu, Jinsong wrote:
> Jan,
>
> Any comments? I feel some confused about your point 'disable cpuid
> feature for older machine type
On Fri, Mar 09, 2012 at 12:17:22PM +0800, Amos Kong wrote:
> Boot up qemu-kvm guest with 232 multiple functions disks, qemu
> will report a ENOSPC error, it's not good to statically increase
> iobus array. This patchset makes kvm_io_range array can be
> resized dynamically, and change dev limit to
From: Jan Kiszka
The upstream version is feature-equivalent and covers more corner cases.
Signed-off-by: Jan Kiszka
---
As the upstream merge was not successful, this also unbreaks XP etc.
over current qemu-kvm.
.gitignore |1 -
Makefile |1 -
Makefi
From: Jan Kiszka
There is no need for an explicit kvm_arch_reset_vcpu on arch cpu init
anymore, kvm_init_vcpu does it already. Call the remaining
kvm_update_ioport_access directly from kvm_arch_init_vcpu.
Signed-off-by: Jan Kiszka
---
This depends on the TPR switch-over patch.
qemu-kvm-x86.c
On Thu, Mar 08, 2012 at 11:56:56AM +, Daniel P. Berrange wrote:
> On Thu, Mar 08, 2012 at 01:52:45PM +0200, Avi Kivity wrote:
> > On 03/08/2012 01:36 PM, Daniel P. Berrange wrote:
> > > On Thu, Mar 08, 2012 at 01:28:56PM +0200, Avi Kivity wrote:
> > > > On 03/08/2012 12:15 PM, Wen Congyang wrot
On Thu, Mar 08, 2012 at 06:07:56PM +0800, Jason Wang wrote:
> Also count the exits of fast-path.
>
> Signed-off-by: Jason Wang
> ---
> arch/x86/kvm/svm.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe
On Thu, 2012-03-08 at 11:10 +0100, Jan Kiszka wrote:
> This enables support for the host IRQ sharing support via PCI-2.3
> interrupt masking. See the patches for details.
>
> Patch 1 & 3 could be considered for uq/master although we have no use
> case for the changes in upstream yet.
>
> Changes
On Thu, Mar 08, 2012 at 01:17:44PM +0200, Avi Kivity wrote:
> Deprecated in favour of tracepoints.
>
> Signed-off-by: Avi Kivity
> ---
> Documentation/feature-removal-schedule.txt |7 +++
> 1 files changed, 7 insertions(+), 0 deletions(-)
Applied, thanks.
--
To unsubscribe from this li
On Thu, Mar 08, 2012 at 11:10:23AM +0100, Jan Kiszka wrote:
> This enables support for the host IRQ sharing support via PCI-2.3
> interrupt masking. See the patches for details.
>
> Patch 1 & 3 could be considered for uq/master although we have no use
> case for the changes in upstream yet.
>
> C
This series is a follow up to the previous thread here:
http://lists.openwall.net/netdev/2012/02/29/31
There are some significant changes in this series. First
I add two NTF_XXX bits to signal if the PF_BRIDGE netlink
command should be parsed by the embedded bridge or the
SW bridge. The insight h
This adds a dev_uc_add_excl() call similar to the original
dev_uc_add() except it sets the global bit. With this
change the reference count will not be bumped and -EEXIST
will be returned if a duplicate address exists.
This is useful for drivers that support SR-IOV and want
to manage the unicast l
This adds a generic dump routine drivers can call. It
should be sufficient to handle any bridging model that
uses the unicast address list. This should be most SR-IOV
enabled NICs.
Signed-off-by: John Fastabend
---
net/core/rtnetlink.c | 56 ++
Enable FDB ops on ixgbe when in SR-IOV mode.
Signed-off-by: John Fastabend
---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 59 +
1 files changed, 59 insertions(+), 0 deletions(-)
diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
b/drivers/net/ethernet/in
Resending this patch with a new title apparently "PF_BRIDGE:RTM_XXX
FDB hooks" looks like spam. Sorry for the noise if you get a dup.
---
net: add generic PF_BRIDGE:RTM_XXX FDB hooks
This adds two new flags NTF_MASTER and NTF_LOWERDEV that can
now be used to specify where PF_BRIDGE netlink comman
On Fri, Mar 09, 2012 at 10:35:27PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka
>
> The upstream version is feature-equivalent and covers more corner cases.
>
> Signed-off-by: Jan Kiszka
> ---
>
> As the upstream merge was not successful, this also unbreaks XP etc.
> over current qemu-kvm.
App
On Friday, March 09, 2012 11:56:36 AM you wrote:
> On Thu, Mar 8, 2012 at 5:48 PM, George Bottas wrote:
> > I have a question regarding changing the queue size that is set in
> > virtio_blk_init(). The current value is 128, which results in setting
> > the queue depth in the Windows guest device t
On Thu, Mar 08, 2012 at 04:44:24PM -0500, Christoffer Dall wrote:
> Any news on the status of this?
>
> On Thu, Feb 9, 2012 at 8:45 PM, Alexander Graf wrote:
> >
> > On 10.02.2012, at 02:40, Christoffer Dall wrote:
> >
> >> The kvm_vcpu_kick function performs roughly the same funcitonality on
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 09.03.2012 21:52, schrieb Jan Kiszka:
> Andreas, do you expect CPU devices to be ready for qemu 1.1? We
> would need them to pass a feature exclusion mask from
> machine.compat_props to the (x86) CPU init code.
I was sure hoping to!
Marcelo and
> Enable FDB ops on ixgbe when in SR-IOV mode.
>
> Signed-off-by: John Fastabend
Will all this break anything on the vf client? What if the vf is running
a bridge.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majord
On 3/9/2012 7:48 PM, Stephen Hemminger wrote:
>
>> Enable FDB ops on ixgbe when in SR-IOV mode.
>>
>> Signed-off-by: John Fastabend
>
> Will all this break anything on the vf client? What if the vf is running
> a bridge.
No shouldn't break anything.
Actually, implementing these ops in the VF d
46 matches
Mail list logo
