|
Re: reminder: IO Visor TSC and Dev Members Call
Hi Brendan,
Does this mean the time is 12 midday Santa Clara time? (I won't even venture am/pm !)
Thanks,
/Billy.
Hi Brendan,
Does this mean the time is 12 midday Santa Clara time? (I won't even venture am/pm !)
Thanks,
/Billy.
|
By
O Mahony, Billy <billy.o.mahony@...>
·
#121
·
|
|
Re: reminder: IO Visor TSC and Dev Members Call
What I actually meant was (11 am pacific)
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=3&day=30&hour=18&min=0&sec=0&p1=886
Blame daylight "saving" time, which saves
What I actually meant was (11 am pacific)
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=3&day=30&hour=18&min=0&sec=0&p1=886
Blame daylight "saving" time, which saves
|
By
Brenden Blanco <bblanco@...>
·
#122
·
|
|
Re: reminder: IO Visor TSC and Dev Members Call
Perfect!
From: Brenden Blanco [mailto:bblanco@...]
Sent: Wednesday, March 30, 2016 3:50 PM
To: O Mahony, Billy <billy.o.mahony@...>
Cc: iovisor-dev@...
Subject: RE: [iovisor-dev] reminder: IO Visor
Perfect!
From: Brenden Blanco [mailto:bblanco@...]
Sent: Wednesday, March 30, 2016 3:50 PM
To: O Mahony, Billy <billy.o.mahony@...>
Cc: iovisor-dev@...
Subject: RE: [iovisor-dev] reminder: IO Visor
|
By
O Mahony, Billy <billy.o.mahony@...>
·
#123
·
|
|
ietf drafts
ILA
By
Alexei Starovoitov
·
#124
·
|
|
minutes: IO Visor TSC and Dev Members Call
Hi All,
Thanks for attending the meeting today. Here are the things I took note of:
(Alexei)
Tracepoint patches are almost ready, to be posted when net-next opens
- Can be faster than kprobes when
Hi All,
Thanks for attending the meeting today. Here are the things I took note of:
(Alexei)
Tracepoint patches are almost ready, to be posted when net-next opens
- Can be faster than kprobes when
|
By
Brenden Blanco <bblanco@...>
·
#125
·
|
|
"invalid mem access" when inspecting packets from probe
Hi,
I want to efficiently obtain incoming http request rates by process.
For that I am writing a proof of concept [0] based on
Hi,
I want to efficiently obtain incoming http request rates by process.
For that I am writing a proof of concept [0] based on
|
By
Alfonso Acosta <fons@...>
·
#126
·
|
|
Re: "invalid mem access" when inspecting packets from probe
PS: I am running kernel 4.4.2 and the nightly bcc.
PS: I am running kernel 4.4.2 and the nightly bcc.
|
By
Alfonso Acosta <fons@...>
·
#127
·
|
|
Re: "invalid mem access" when inspecting packets from probe
I wasn't thinking. I first need to read the field and then the pointed data.
u8 data[4] = {};
void* datap = 0;
bpf_probe_read(&datap, sizeof(datap), &skb->data);
bpf_probe_read(&data, sizeof(data),
I wasn't thinking. I first need to read the field and then the pointed data.
u8 data[4] = {};
void* datap = 0;
bpf_probe_read(&datap, sizeof(datap), &skb->data);
bpf_probe_read(&data, sizeof(data),
|
By
Alfonso Acosta <fons@...>
·
#128
·
|
|
Why do some bcc scripts run smoothly while some not?
Hi all,
My OS is RHEL 7.2 (kernel version is 3.10). To use bcc/bpf, I download and install the newest 4.5 kernel.
After installing bcc, I find some scripts run smoothly:
some run with warning:
While
Hi all,
My OS is RHEL 7.2 (kernel version is 3.10). To use bcc/bpf, I download and install the newest 4.5 kernel.
After installing bcc, I find some scripts run smoothly:
some run with warning:
While
|
By
Nan Xiao <xiaonan830818@...>
·
#129
·
|
|
Re: Why do some bcc scripts run smoothly while some not?
Hello Nan Xiao,
Please see responses inline. Hope this helps.
On Fri, Apr 8, 2016 at 2:18 AM, Nan Xiao via iovisor-dev <iovisor-dev@...> wrote:
This occurs because kernel (generally built with gcc)
Hello Nan Xiao,
Please see responses inline. Hope this helps.
On Fri, Apr 8, 2016 at 2:18 AM, Nan Xiao via iovisor-dev <iovisor-dev@...> wrote:
This occurs because kernel (generally built with gcc)
|
By
Brenden Blanco <bblanco@...>
·
#130
·
|
|
Re: Why do some bcc scripts run smoothly while some not?
Hi Brenden,
Thanks very much for your detailed explanations!
Best Regards
Nan Xiao
Hi Brenden,
Thanks very much for your detailed explanations!
Best Regards
Nan Xiao
|
By
Nan Xiao <xiaonan830818@...>
·
#131
·
|
|
Can we use IOVISOR for virtual machine introspection.
Hi
I am working on IOVIOSR. I have implemented IOVISOR tools and got the output. But my purpose is different. I am working on libvmi. I have a machine on KVM hyper-visor running on my Ubuntu machine.
Hi
I am working on IOVIOSR. I have implemented IOVISOR tools and got the output. But my purpose is different. I am working on libvmi. I have a machine on KVM hyper-visor running on my Ubuntu machine.
|
By
Tahir Ahmed <tahirahmed1044@...>
·
#132
·
|
|
reminder: IO Visor TSC and Dev Members Call
Hi all,
Please join us for our bi-weekly call. This meeting is open to everybody and completely
Hi all,
Please join us for our bi-weekly call. This meeting is open to everybody and completely
|
By
Brenden Blanco <bblanco@...>
·
#133
·
|
|
autofdo video
FYI, as discussed in the conf call:
https://www.youtube.com/watch?v=26SrOC6MXWg
FYI, as discussed in the conf call:
https://www.youtube.com/watch?v=26SrOC6MXWg
|
By
Hannes Frederic Sowa
·
#134
·
|
|
bpf version of this sample
Hello,
if a bpf counterpart of this example would be possible, it would be
really cool:
http://lxr.free-electrons.com/source/samples/hw_breakpoint/data_breakpoint.c
Bye,
Hannes
Hello,
if a bpf counterpart of this example would be possible, it would be
really cool:
http://lxr.free-electrons.com/source/samples/hw_breakpoint/data_breakpoint.c
Bye,
Hannes
|
By
Hannes Frederic Sowa
·
#135
·
|
|
Re: bpf version of this sample
Hello,
Care must be taken, as the code path in this example as-is is only valid from process context, as mutexes will be taken during the installation of the watch point. This actually renders it a
Hello,
Care must be taken, as the code path in this example as-is is only valid from process context, as mutexes will be taken during the installation of the watch point. This actually renders it a
|
By
Hannes Frederic Sowa
·
#136
·
|
|
Re: bpf version of this sample
<iovisor-dev@...> wrote:
do you propose to let programs register such hw breakpoints to point to
other programs?
That will be hard to achieve as you said due to mutexes...
but we can
<iovisor-dev@...> wrote:
do you propose to let programs register such hw breakpoints to point to
other programs?
That will be hard to achieve as you said due to mutexes...
but we can
|
By
Alexei Starovoitov
·
#137
·
|
|
Re: bpf version of this sample
Actually for network debugging it would be nice if we could classify an skb
e.g. from XDP (when passed to stack) or cls_bpf ingress, and tell the kernel
that if this particular skb changes e.g. its
Actually for network debugging it would be nice if we could classify an skb
e.g. from XDP (when passed to stack) or cls_bpf ingress, and tell the kernel
that if this particular skb changes e.g. its
|
By
Daniel Borkmann
·
#138
·
|
|
Re: bpf version of this sample
Yes, that a eBPF program can register such a hw breakpoint within the kernel after checking for some conditions. The CPU debug registers aren't very big thus we probably can't use more than 4
Yes, that a eBPF program can register such a hw breakpoint within the kernel after checking for some conditions. The CPU debug registers aren't very big thus we probably can't use more than 4
|
By
Hannes Frederic Sowa
·
#139
·
|
|
minutes: IO Visor TSC and Dev members call
Thanks all for another good discussion.
There are two major updates this week.
== Tracepoints
First, from Alexei, the infrastructure to attach bpf programs to tracepoints
has been merged in net-next.
Thanks all for another good discussion.
There are two major updates this week.
== Tracepoints
First, from Alexei, the infrastructure to attach bpf programs to tracepoints
has been merged in net-next.
|
By
Brenden Blanco <bblanco@...>
·
#140
·
|