All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] unnecessary removal of guest console characters
Date: Mon, 21 Apr 2008 17:28:27 +0100	[thread overview]
Message-ID: <480CC0AB.20001@eu.citrix.com> (raw)
In-Reply-To: <C429295A.1F98C%keir.fraser@eu.citrix.com>

[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]

Hi all,
I am attaching a patch that adds a new command line option to xenconsoled:

-o, --overflow-data=discard|keep

this option changes the behaviour when dealing with data that overflow
the max capacity of the buffer.
If overflow-data is set to discard (the default), the current behaviour
is used: we discard some data in the middle of the buffer.
If overflow-data is set to keep, we stop listening to the ring until we
free some space in the buffer.
This can cause the ring to fill up and the guest kernel internal buffer
to fill up as well. When this happens the guest kernel stops reading
characters from the console device so the application generating data
hangs. When xenconsoled resumes reading from the ring, the guest kernel
will be able to resume reading from the console device as well. At that
point the guest application will be allowed to continue.

Regards,

Stefano Stabellini

Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>

Keir Fraser wrote:
> On 14/4/08 15:14, "Samuel Thibault" <samuel.thibault@eu.citrix.com> wrote:
> 
>> Keir Fraser, le Fri 11 Apr 2008 16:46:48 +0100, a écrit :
>>> The 'application' in this case is the kernel.
>> Mmm, in my understanding of printk, it is not blocking for the kernel,
>> and if a console is not able to catch up, the data simply gets
>> discarded (see __call_console_drivers, which doesn't check the result
>> of con->write(), which can hence be even 0 if the console is really
>> completely stuck).
> 
> Actually I was worried that we might depend on the ring being drained in a
> timely fashion in our own console driver implementation in Linux. Actually I
> think we don't (except that the handling of x_char looks suspect). Still, I
> don't know whether other guest types depend on the current behaviour. We
> could make the behaviour switchable I suppose.
> 
>  -- Keir
> 
> 




[-- Attachment #2: console-overflow2.patch --]
[-- Type: text/x-diff, Size: 3245 bytes --]

diff -r 84b5dee690f5 tools/console/daemon/io.c
--- a/tools/console/daemon/io.c	Mon Apr 21 14:59:25 2008 +0100
+++ b/tools/console/daemon/io.c	Mon Apr 21 16:51:32 2008 +0100
@@ -63,6 +63,7 @@ extern int log_time_hv;
 extern int log_time_hv;
 extern int log_time_guest;
 extern char *log_dir;
+extern int discard_overflowed_data;
 
 static int log_time_hv_needts = 1;
 static int log_time_guest_needts = 1;
@@ -201,7 +202,7 @@ static void buffer_append(struct domain 
 			      dom->domid, errno, strerror(errno));
 	}
 
-	if (buffer->max_capacity &&
+	if (discard_overflowed_data && buffer->max_capacity &&
 	    buffer->size > buffer->max_capacity) {
 		/* Discard the middle of the data. */
 
@@ -228,6 +229,11 @@ static void buffer_advance(struct buffer
 	if (buffer->consumed == buffer->size) {
 		buffer->consumed = 0;
 		buffer->size = 0;
+		if (buffer->max_capacity &&
+		    buffer->capacity > buffer->max_capacity) {
+			buffer->data = realloc(buffer->data, buffer->max_capacity);
+			buffer->capacity = buffer->max_capacity;
+		}
 	}
 }
 
@@ -1005,9 +1011,13 @@ void handle_io(void)
 				    d->next_period < next_timeout)
 					next_timeout = d->next_period;
 			} else if (d->xce_handle != -1) {
-				int evtchn_fd = xc_evtchn_fd(d->xce_handle);
-				FD_SET(evtchn_fd, &readfds);
-				max_fd = MAX(evtchn_fd, max_fd);
+				if (discard_overflowed_data ||
+				    !d->buffer.max_capacity ||
+				    d->buffer.size < d->buffer.max_capacity) {
+					int evtchn_fd = xc_evtchn_fd(d->xce_handle);
+					FD_SET(evtchn_fd, &readfds);
+					max_fd = MAX(evtchn_fd, max_fd);
+				}
 			}
 
 			if (d->master_fd != -1) {
diff -r 84b5dee690f5 tools/console/daemon/main.c
--- a/tools/console/daemon/main.c	Mon Apr 21 14:59:25 2008 +0100
+++ b/tools/console/daemon/main.c	Mon Apr 21 16:51:54 2008 +0100
@@ -38,6 +38,7 @@ int log_time_hv = 0;
 int log_time_hv = 0;
 int log_time_guest = 0;
 char *log_dir = NULL;
+int discard_overflowed_data = 1;
 
 static void handle_hup(int sig)
 {
@@ -46,7 +47,7 @@ static void handle_hup(int sig)
 
 static void usage(char *name)
 {
-	printf("Usage: %s [-h] [-V] [-v] [-i] [--log=none|guest|hv|all] [--log-dir=DIR] [--pid-file=PATH] [-t, --timestamp=none|guest|hv|all]\n", name);
+	printf("Usage: %s [-h] [-V] [-v] [-i] [--log=none|guest|hv|all] [--log-dir=DIR] [--pid-file=PATH] [-t, --timestamp=none|guest|hv|all] [-o, --overflow-data=discard|keep]\n", name);
 }
 
 static void version(char *name)
@@ -56,7 +57,7 @@ static void version(char *name)
 
 int main(int argc, char **argv)
 {
-	const char *sopts = "hVvit:";
+	const char *sopts = "hVvit:o:";
 	struct option lopts[] = {
 		{ "help", 0, 0, 'h' },
 		{ "version", 0, 0, 'V' },
@@ -66,6 +67,7 @@ int main(int argc, char **argv)
 		{ "log-dir", 1, 0, 'r' },
 		{ "pid-file", 1, 0, 'p' },
 		{ "timestamp", 1, 0, 't' },
+		{ "overflow-data", 1, 0, 'o'},
 		{ 0 },
 	};
 	bool is_interactive = false;
@@ -119,6 +121,13 @@ int main(int argc, char **argv)
 				log_time_hv = 0;
 			}
 			break;
+		case 'o':
+			if (!strcmp(optarg, "keep")) {
+				discard_overflowed_data = 0;
+			} else if (!strcmp(optarg, "discard")) {
+				discard_overflowed_data = 1;
+			}
+			break;
 		case '?':
 			fprintf(stderr,
 				"Try `%s --help' for more information\n",



[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

       reply	other threads:[~2008-04-21 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C429295A.1F98C%keir.fraser@eu.citrix.com>
2008-04-21 16:28 ` Stefano Stabellini [this message]
2008-04-11 13:46 [PATCH] unnecessary removal of guest console characters Stefano Stabellini
2008-04-11 15:03 ` Keir Fraser
2008-04-11 15:11   ` Samuel Thibault
2008-04-11 15:46     ` Keir Fraser

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=480CC0AB.20001@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.