Displaying 8 results from an estimated 8 matches for "max_capac".
2019 May 24
0
[PATCH] VMCI: Fix integer overflow in VMCI handle arrays
...ndle_arr_calc_size(u32 capacity)
{
- return sizeof(struct vmci_handle_arr) +
+ return VMCI_HANDLE_ARRAY_HEADER_SIZE +
capacity * sizeof(struct vmci_handle);
}
-struct vmci_handle_arr *vmci_handle_arr_create(size_t capacity)
+struct vmci_handle_arr *vmci_handle_arr_create(u32 capacity, u32 max_capacity)
{
struct vmci_handle_arr *array;
+ if (max_capacity == 0 || capacity > max_capacity)
+ return NULL;
+
if (capacity == 0)
- capacity = VMCI_HANDLE_ARRAY_DEFAULT_SIZE;
+ capacity = min((u32)VMCI_HANDLE_ARRAY_DEFAULT_CAPACITY,
+ max_capacity);
array = kmalloc(handle_arr_c...
2005 Aug 30
4
Re: [Xen-changelog] New console transport and update xenconsoled.
...nclude <unistd.h>
> #include <termios.h>
>+#include <stdarg.h>
>+#include <sys/ioctl.h>
>+#include <sys/mman.h>
>
> #define MAX(a, b) (((a) > (b)) ? (a) : (b))
> #define MIN(a, b) (((a) < (b)) ? (a) : (b))
>@@ -48,41 +51,6 @@
> size_t max_capacity;
> };
>
>-static void buffer_append(struct buffer *buffer, const void *data, size_t size)
>-{
>- if ((buffer->capacity - buffer->size) < size) {
>- buffer->capacity += (size + 1024);
>- buffer->data = realloc(buffer->data, buffer->capacity);
>- if...
2010 Aug 09
1
[PATCH 1 of 4] xenconsoled: do not write the pty under serial
...+0100
@@ -451,27 +451,6 @@ static int domain_create_tty(struct doma
free(data);
}
free(path);
- }
-
- success = asprintf(&path, "%s/limit", dom->serialpath) != -1;
- if (!success)
- goto out;
- data = xs_read(xs, XBT_NULL, path, &len);
- if (data) {
- dom->buffer.max_capacity = strtoul(data, 0, 0);
- free(data);
- }
- free(path);
-
- success = asprintf(&path, "%s/tty", dom->serialpath) != -1;
- if (!success)
- goto out;
- success = xs_write(xs, XBT_NULL, path, slave, strlen(slave));
- free(path);
- if (!success)
- goto out;
-
- if (dom->use_con...
2013 Jan 03
20
[PATCH] Switch to poll in xenconsoled's io loop.
...d->next_period) {
+ if (now > d->next_period) {
d->next_period = now + RATE_LIMIT_PERIOD;
if (d->event_count >= RATE_LIMIT_ALLOWANCE) {
(void)xc_evtchn_unmask(d->xce_handle, d->local_port);
@@ -1006,74 +1013,73 @@ void handle_io(void)
!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);
+ SET_FDS(evtchn_fd, POLLIN);
}
}
if (d->master_fd != -1) {
+ short events...
2008 Jun 30
0
[PATCH] qemu xen-console, limit buffering
...16 0 291m 231m 2448 R 15 17.0
0:16.34 qemu-dm
Much later: (72.8% mem usage)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10281 root 15 0 1052m 989m 2448 S 10 72.8
1:13.25 qemu-dm
Attached patch sets dom->buffer.max_capacity to xend configured limit.
Please apply to xen-unstable tip.
Signed-off-by: Pat Campbell <plc@novell.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2007 Oct 24
16
PATCH 0/10: Merge PV framebuffer & console into QEMU
The following series of 10 patches is a merge of the xenfb and xenconsoled
functionality into the qemu-dm code. The general approach taken is to have
qemu-dm provide two machine types - one for xen paravirt, the other for
fullyvirt. For compatability the later is the default. The goals overall
are to kill LibVNCServer, remove alot of code duplication and/or parallel
impls of the same concepts, and
2006 Feb 17
16
Booking system
Hi!
I''m planning a booking system in rails, and I have the following issue:
There will be room_types. I can implement this with STI in the rooms
table, or with a separate table room_types. Each room type will have its
special features.
For example, a double room can be:
--
Posted via http://www.ruby-forum.com/.
2011 Jul 21
51
Linux Stubdom Problem
2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>:
> CC''ing Tim and xen-devel
>
> On Mon, 18 Jul 2011, Jiageng Yu wrote:
>> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>:
>> > On Fri, 15 Jul 2011, Jiageng Yu wrote:
>> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>:
>> >> > 2011/7/15