From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6248] Allow devices be notified of link status change (Mark McLoughlin)
Date: Thu, 08 Jan 2009 19:45:04 +0000 [thread overview]
Message-ID: <E1LL0oS-0007L2-4D@cvs.savannah.gnu.org> (raw)
Revision: 6248
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6248
Author: aliguori
Date: 2009-01-08 19:45:03 +0000 (Thu, 08 Jan 2009)
Log Message:
-----------
Allow devices be notified of link status change (Mark McLoughlin)
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Modified Paths:
--------------
trunk/net.c
trunk/net.h
Modified: trunk/net.c
===================================================================
--- trunk/net.c 2009-01-08 19:44:06 UTC (rev 6247)
+++ trunk/net.c 2009-01-08 19:45:03 UTC (rev 6248)
@@ -1718,6 +1718,9 @@
term_printf("invalid link status '%s'; only 'up' or 'down' valid\n",
up_or_down);
+ if (vc->link_status_changed)
+ vc->link_status_changed(vc);
+
return 1;
}
Modified: trunk/net.h
===================================================================
--- trunk/net.h 2009-01-08 19:44:06 UTC (rev 6247)
+++ trunk/net.h 2009-01-08 19:45:03 UTC (rev 6248)
@@ -9,12 +9,15 @@
typedef struct VLANClientState VLANClientState;
+typedef void (LinkStatusChanged)(VLANClientState *);
+
struct VLANClientState {
IOReadHandler *fd_read;
IOReadvHandler *fd_readv;
/* Packets may still be sent if this returns zero. It's used to
rate-limit the slirp code. */
IOCanRWHandler *fd_can_read;
+ LinkStatusChanged *link_status_changed;
int link_down;
void *opaque;
struct VLANClientState *next;
reply other threads:[~2009-01-08 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LL0oS-0007L2-4D@cvs.savannah.gnu.org \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).